GitHub
Repository access, branch management, and Git workflows for Olive Code projects.
All Olive Code project code is hosted on GitHub. When you claim a project, you're added as a collaborator to the repository and a personal branch is created for your work.
Make sure your GitHub username is set in your account settings before claiming a project. This is used to grant you repository access and create your branch.
- Find Repository Link
The repository URL is shown on the project details page in the Worker Dashboard.
- Clone the Repository
Use
git clone [repository-url]to download the code locally. - Checkout Your Branch
Switch to your worker branch with
git checkout worker-[your-pseudonym]
Olive Code repositories use a consistent branch naming convention:
| Branch Pattern | Purpose | Who Uses It |
|---|---|---|
main | Production code | Automated deployments only |
staging | Pre-production testing | Review/merge process |
worker-[pseudonym] | Worker development | You (the worker) |
The main and staging branches are protected. You can only push to your worker branch. Changes to production go through the formal promotion process.
Commands you'll use frequently:
# Clone a repository git clone https://github.com/[org]/[repo].git # Check current branch git branch # Switch to your worker branch git checkout worker-[pseudonym] # Pull latest changes git pull origin worker-[pseudonym] # Stage all changes git add . # Commit with a message git commit -m "Add user authentication flow" # Push changes git push origin worker-[pseudonym] # Check status of your changes git status # View commit history git log --oneline
- Commit often – Small, focused commits are easier to review and revert if needed.
- Write clear commit messages – Describe what changed and why.
- Pull before pushing – Avoid conflicts by pulling the latest changes first.
- Don't commit secrets – Use environment variables for API keys and passwords.
- Review your diffs – Check
git diffbefore committing.