Skip to content

Latest commit

 

History

History
180 lines (128 loc) · 5.59 KB

CONTRIBUTING.md

File metadata and controls

180 lines (128 loc) · 5.59 KB
Raw

How to Contribute

We'd love to accept your patches and contributions to this project.

Before you begin

Sign our Contributor License Agreement

Contributions to this project must be accompanied by a Contributor License Agreement (CLA). You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project.

If you or your current employer have already signed the Google CLA (even if it was for a different project), you probably don't need to do it again.

Visit https://cla.developers.google.com/ to see your current agreements or to sign a new one.

Review our Community Guidelines

This project follows Google's Open Source Community Guidelines.

Contribution process

We follow the fork and branch workflow.

There will be three Git repositories involved:

  1. upstream - the ServiceWeaver repository on GitHub.
  2. origin - your GitHub fork of upstream. This repository will typically be at a URL that looks like github.com/_your_user_name_/weaver
  3. local - your local clone of origin

First time setup

Follow these steps to get ready for making changes to ServiceWeaver. These steps are only needed once and not for subsequent changes you might want to make:

  1. Fork the ServiceWeaver repository on GitHub to create origin. Visit ServiceWeaver GitHub repository and click the Fork button.

  2. Make a local clone of your fork.

    git clone [email protected]:_your_user_name_/weaver.git

  3. Add a remote pointing from local to upstream.

    cd weaver
git remote add upstream [email protected]:ServiceWeaver/weaver.git

Making changes

Here is a detailed outline of the steps needed to make changes to Service Weaver.

  1. Make a local branch in your clone and pull any recent changes into it.

    git switch -c my_branch  # Pick a name appropriate to your work
git pull upstream main

  2. Make changes and commit to local branch.

    # ... editing, testing, ... 
git commit ...

  3. Pull any changes that may have been made in the upstream repository main branch.

    git switch my_branch
git pull --rebase upstream main

    Note that this command may result in merge conflicts. Fix those if needed.

  4. Push your branch to the corresponding branch in your fork (the origin repository).

    git switch my_branch
git push origin my_branch

  5. Select the branch you are working on in the drop-down menu of branches on https://github.com/_your_user_name_/weaver . Then hit the Compare and pull request button.

  6. Respond to feedback, which may involve making new commits. If you made any changes, push them to github again.

    git switch my_branch
git push origin my_branch

    Repeat as necessary until all feedback has been handled.

    Note: the preceding approach will cause the pull request to become a sequence of commits. Some people like to keep just a single commit that is amended as changes are made. If you are amending commits that had already been pushed, you will have to add --force to the git push command above.

  7. Once reviewers are happy, pull any main branch changes that may have happened since step 3.

    git switch my_branch
git pull --rebase upstream main

    If some changes were pulled, push again to the PR, but this time you will need to force push since the rebase above will have rewritten your commits.

    git switch my_branch
git push --force origin my_branch

  8. Ask somebody who has permissions (or do it yourself if you have permissions) to merge your branch into the main branch of the upstream repository. The reviewer may do this without being asked.

    Select the Squash and merge option on https://github.com/ServiceWeaver/weaver or use the command line instructions found on that page. Edit the commit message as appropriate for the squashed commit.

  9. Delete the branch from origin:

    git push origin --delete my_branch

  10. Delete the branch from local

    git switch main
git branch -D my_branch

Code Reviews

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.

To make sure changes are well coordinated, we ask you to discuss any significant change prior to sending a pull request. To do so, either file a new issue or claim an existing one.

What to contribute to?

Here are the current areas where the community contributions would be most valuable:

  • Implement deployers for platforms other than local, SSH, and GKE.
  • Bug fixes for the existing libraries.
  • Non-Go language support. (Note: please reach out to us on our [google_group][Google Group], to coordinate development. We will likely require a fair bit of API and language-integration design discussion before the implementation starts.)