Content-Length: 1413 | pFad | http://github.com/github/github-mcp-server/pull/640.patch

thub.com From cea37522a3fae1691277cc0b43cdf6d4144c2987 Mon Sep 17 00:00:00 2001 From: Sam Morrow Date: Fri, 4 Jul 2025 16:49:44 +0200 Subject: [PATCH] fix: stale information in CONTRIBUTING.md --- CONTRIBUTING.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6fa9c2ebe..314e4e0b2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,14 +19,12 @@ These are one time installations required to be able to test your changes locall ## Submitting a pull request -> **Important**: Please open your pull request against the `next` branch, not `main`. The `next` branch is where we integrate new features and changes before they are merged to `main`. - 1. [Fork][fork] and clone the repository 1. Make sure the tests pass on your machine: `go test -v ./...` 1. Make sure linter passes on your machine: `golangci-lint run` 1. Create a new branch: `git checkout -b my-branch-name` 1. Make your change, add tests, and make sure the tests and linter still pass -1. Push to your fork and [submit a pull request][pr] targeting the `next` branch +1. Push to your fork and [submit a pull request][pr] targeting the `main` branch 1. Pat yourself on the back and wait for your pull request to be reviewed and merged. Here are a few things you can do that will increase the likelihood of your pull request being accepted:

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!