Working with git

Cloning Projects

Let’s get started by creating a workspace for the project. Many contributors work with Go and follow their convention.

mkdir -p ${GOPATH}/src/ && cd $_

Once you have a workspace, you’ll want to clone the relevant projects. Most people contribute to depscloud but will also need deploy for docker.

git clone [email protected]:depscloud/depscloud.git    # source code
git clone [email protected]:depscloud/deploy.git       # deployment config

git clone [email protected]:depscloud/   # website
git clone [email protected]:depscloud/api.git          # api and sdk


The most common way you will likely create a branch is through the use of a GitHub issue within the repository. To create a branch for GitHub issue #11, simply create a branch with the name gh-11.

git checkout -b gh-11

Forking and Submitting Pull Requests

By and large, forks are used to submit pull requests to the upstream repositories.

After a project has been cloned, you will need to add your fork as a remote.

git remote add <myuser> [email protected]:<myuser>/<project>.git

By doing this, you’re able to maintain two references: one for upstream updates and one for your set of changes. When pushing a branch to, you can specify the -u option to have your local branch track a specific remote.

git push -u <myuser> gh-11

From here, all git push operations will default to using your fork. After a branch has been pushed, you can use pull requests to have your code reviewed by the team.

Last modified October 26, 2020: darken up lines (141fe72)