-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into addRepositorySecurityAdvisoryAPIs
- Loading branch information
Showing
55 changed files
with
1,827 additions
and
1,089 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,8 @@ | ||
*.sh | ||
!/script/*.sh | ||
*.test | ||
coverage.out | ||
/bin | ||
# intellij files | ||
.idea/ | ||
vendor/ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
run: | ||
build-tags: | ||
- integration | ||
timeout: 10m | ||
linters: | ||
enable: | ||
- dogsled | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,68 +31,62 @@ are more sensitive, emailed to <[email protected]>. | |
|
||
## Submitting a patch ## | ||
|
||
1. It's generally best to start by opening a new issue describing the bug or | ||
feature you're intending to fix. Even if you think it's relatively minor, | ||
it's helpful to know what people are working on. Mention in the initial | ||
issue that you are planning to work on that bug or feature so that it can | ||
be assigned to you. | ||
|
||
1. Follow the normal process of [forking][] the project, and setup a new | ||
branch to work in. It's important that each group of changes be done in | ||
separate branches in order to ensure that a pull request only includes the | ||
commits related to that bug or feature. | ||
|
||
1. Go makes it very simple to ensure properly formatted code, so always run | ||
`go fmt` on your code before committing it. You should also run | ||
[go vet][] over your code. this will help you find common style issues | ||
within your code and will keep styling consistent within the project. | ||
|
||
1. Any significant changes should almost always be accompanied by tests. The | ||
project already has good test coverage, so look at some of the existing | ||
tests if you're unsure how to go about it. [gocov][] and [gocov-html][] | ||
are invaluable tools for seeing which parts of your code aren't being | ||
exercised by your tests. | ||
|
||
1. Please run: | ||
* `go generate github.com/google/go-github/...` | ||
* `go test github.com/google/go-github/...` | ||
* `go vet github.com/google/go-github/...` | ||
|
||
The `go generate ./...` command will update or generate certain files, and the | ||
resulting changes should be included in your pull request. | ||
|
||
The `go test ./...` command will run tests inside your code. This will help you | ||
spot places where code might be faulty before committing. | ||
|
||
And finally, the `go vet ./...` command will check linting and styling over your | ||
code, keeping the project consistent formatting-wise. | ||
|
||
In any case, it is always a good idea to read [official Go documentation][] when working | ||
on this project, as the definition of tools and commands of the Go programming | ||
language is described in further detail there. | ||
|
||
1. Do your best to have [well-formed commit messages][] for each change. | ||
This provides consistency throughout the project, and ensures that commit | ||
messages are able to be formatted properly by various git tools. | ||
|
||
1. Finally, push the commits to your fork and submit a [pull request][]. | ||
Before pushing commits, it is highly advised to check for generated files | ||
that were either created or modified for the sake of your commit. Running | ||
`go generate -x ./...` should return a log of modified generated files that should | ||
be included alongside the manually written code in the commit. | ||
**NOTE:** Please do not use force-push on PRs in this repo, as it makes | ||
it more difficult for reviewers to see what has changed since the last | ||
code review. | ||
|
||
[official Go documentation]: https://pkg.go.dev/std | ||
1. It's generally best to start by opening a new issue describing the bug or | ||
feature you're intending to fix. Even if you think it's relatively minor, | ||
it's helpful to know what people are working on. Mention in the initial issue | ||
that you are planning to work on that bug or feature so that it can be | ||
assigned to you. | ||
|
||
2. Follow the normal process of [forking][] the project, and set up a new branch | ||
to work in. It's important that each group of changes be done in separate | ||
branches in order to ensure that a pull request only includes the commits | ||
related to that bug or feature. | ||
|
||
3. Any significant changes should almost always be accompanied by tests. The | ||
project already has good test coverage, so look at some of the existing tests | ||
if you're unsure how to go about it. Coverage is [monitored by codecov.io][], | ||
which flags pull requests that decrease test coverage. This doesn't | ||
necessarily mean that PRs with decreased coverage won't be merged. Sometimes | ||
a decrease in coverage makes sense, but if your PR is flagged, you should | ||
either add tests to cover those lines or add a PR comment explaining the | ||
untested lines. | ||
|
||
4. Run `script/fmt.sh`, `script/test.sh` and `script/lint.sh` to format your code and | ||
check that it passes all tests and linters. `script/lint.sh` may also tell you | ||
that generated files need to be updated. If so, run `script/generate.sh` to | ||
update them. | ||
|
||
5. Do your best to have [well-formed commit messages][] for each change. This | ||
provides consistency throughout the project, and ensures that commit messages | ||
are able to be formatted properly by various git tools. | ||
|
||
6. Finally, push the commits to your fork and submit a [pull request][]. | ||
**NOTE:** Please do not use force-push on PRs in this repo, as it makes it | ||
more difficult for reviewers to see what has changed since the last code | ||
review. We always perform "squash and merge" actions on PRs in this repo, so it doesn't | ||
matter how many commits your PR has, as they will end up being a single commit after merging. | ||
This is done to make a much cleaner `git log` history and helps to find regressions in the code | ||
using existing tools such as `git bisect`. | ||
|
||
[forking]: https://help.github.com/articles/fork-a-repo | ||
[go vet]: https://pkg.go.dev/cmd/vet | ||
[gocov]: https://github.com/axw/gocov | ||
[gocov-html]: https://github.com/matm/gocov-html | ||
[well-formed commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html | ||
[squash]: http://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits | ||
[pull request]: https://help.github.com/articles/creating-a-pull-request | ||
[monitored by codecov.io]: https://codecov.io/gh/google/go-github | ||
|
||
## Scripts ## | ||
|
||
The `script` directory has shell scripts that help with common development | ||
tasks. | ||
|
||
**script/fmt.sh** formats all go code in the repository. | ||
|
||
**script/generate.sh** runs code generators and `go mod tidy` on all modules. With | ||
`--check` it checks that the generated files are current. | ||
|
||
**script/lint.sh** runs linters on the project and checks generated files are | ||
current. | ||
|
||
**script/test.sh** runs tests on all modules. | ||
|
||
## Other notes on code organization ## | ||
|
||
|
@@ -144,5 +138,5 @@ this][modified-comment]. | |
[rebase-comment]: https://github.com/google/go-github/pull/277#issuecomment-183035491 | ||
[modified-comment]: https://github.com/google/go-github/pull/280#issuecomment-184859046 | ||
|
||
**When creating a release, don't forget to update the `Version` constant in `github.go`.** This is used to | ||
**When creating a release, don't forget to update the `Version` constant in `github.go`.** This is used to | ||
send the version in the `User-Agent` header to identify clients to the GitHub API. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.