We'd love your help making Connect better!
If you'd like to add new exported APIs, please open an issue describing your proposal — discussing API changes ahead of time makes pull request review much smoother. In your issue, pull request, and any other communications, please remember to treat your fellow contributors with respect!
Note that you'll need to sign Buf's Contributor License Agreement before we can accept any of your contributions. If necessary, a bot will remind you to accept the CLA when you open your pull request.
Fork, then clone the repository:
mkdir -p $GOPATH/src/github.com/bufbuild
cd $GOPATH/src/github.com/bufbuild
git clone git@github.com:your_github_username/connect-go.git
cd connect-go
git remote add upstream https://github.com/bufbuild/connect-go.git
git fetch upstream
Make sure that the tests and the linters pass (you'll need bash
and the
latest stable Go release installed):
make
Start by creating a new branch for your changes:
cd $GOPATH/src/github.com/bufbuild/connect-go
git checkout main
git fetch upstream
git rebase upstream/main
git checkout -b cool_new_feature
Make your changes, then ensure that make
still passes. (Unless you're
changing protoc-gen-connect-go
, you can use the standard go build ./...
and
go test ./...
while you're coding.) When you're satisfied with your changes,
push them to your fork.
git commit -a
git push origin cool_new_feature
Then use the GitHub UI to open a pull request.
At this point, you're waiting on us to review your changes. We try to respond to issues and pull requests within a few business days, and we may suggest some improvements or alternatives. Once your changes are approved, one of the project maintainers will merge them.
We're much more likely to approve your changes if you:
- Add tests for new functionality.
- Write a good commit message.
- Maintain backward compatibility.