|
| 1 | +# Contributing |
| 2 | + |
| 3 | +We'd love to accept your patches and contributions to this project through the |
| 4 | +process of creating a [pull request][https://github.com/devnw/canary] (**PR**). This document details the |
| 5 | +process of submitting a PR so that it can be reviewed and merged into the |
| 6 | +codebase. It also contains some guidelines for writing good commits, reporting |
| 7 | +issues, and guidelines for project maintainers. |
| 8 | + |
| 9 | +--- |
| 10 | + |
| 11 | +## Reporting issues |
| 12 | + |
| 13 | +Bugs, feature requests, and development-related questions should be directed to |
| 14 | +the specific project's issue tracker or discussion board. |
| 15 | + |
| 16 | +### Bugs |
| 17 | + |
| 18 | +If reporting a bug, please submit an issue and provide as much context as |
| 19 | +possible such as your operating system, architecture, library release version, |
| 20 | +Go version (if applicable), and anything else that might be relevant to the bug. |
| 21 | + |
| 22 | +Fill out as much information as possible in the form provided by the issue |
| 23 | +template. |
| 24 | + |
| 25 | +#### SECURITY BUGS |
| 26 | + |
| 27 | +We take security bugs ***VERY*** seriously! |
| 28 | + |
| 29 | +Please promptly report security related bugs to <security@devnw.com>. Please |
| 30 | +follow [responsible disclosure guidelines][SECURITY.md] when publicizing any security related |
| 31 | +information, ensuring that maintainers are aware of the issue and are able to |
| 32 | +address it promptly. |
| 33 | + |
| 34 | +Please include: |
| 35 | + |
| 36 | +1. Information about the vulnerability |
| 37 | +1. Associated CVEs (if any) |
| 38 | +1. Affected release(s) |
| 39 | +1. Affected package(s) |
| 40 | + |
| 41 | +### Feature Requests |
| 42 | + |
| 43 | +For feature requests, please explain what you're trying to do, and |
| 44 | +how the requested feature would help you do that. |
| 45 | + |
| 46 | +Security related bugs can either be reported in the issue tracker, or if they |
| 47 | +are more sensitive, emailed to <security@devnw.com>. |
| 48 | + |
| 49 | +[responsible disclosure guidelines]: https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html |
| 50 | + |
| 51 | +--- |
| 52 | + |
| 53 | +## Submitting a Pull Request |
| 54 | + |
| 55 | + 1. It's generally best to start by opening a new issue describing the bug or |
| 56 | + feature you're intending to fix. Even if you think it's relatively minor, |
| 57 | + it's helpful to know what people are working on. Mention in the initial |
| 58 | + issue that you are planning to work on that bug or feature so that it can |
| 59 | + be assigned to you. |
| 60 | + |
| 61 | + 1. Follow the normal process of [forking][https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo] the project, and setup a new |
| 62 | + branch to work in. It's important that each group of changes be done in |
| 63 | + separate branches in order to ensure that a pull request only includes the |
| 64 | + commits related to that bug or feature. |
| 65 | + |
| 66 | + 1. This project uses `nix` and `direnv` to manage development environments. |
| 67 | + Please ensure you have both installed and configured on your system. |
| 68 | + See the [development environment documentation](./DEVELOPMENT.md) for more |
| 69 | + information. |
| 70 | +--- |
| 71 | + |
| 72 | +## Maintainer's Guide |
| 73 | + |
| 74 | +(These notes are mostly only for people merging in pull requests.) |
| 75 | + |
| 76 | +It is the responsibility of the maintainer to ensure that the code is passing |
| 77 | +all checks and tests. The maintainer should also ensure that the code is |
| 78 | +consistent with the project's [code style][] and [documentation][]. The |
| 79 | +maintainer should also ensure that the code is well-documented and tested |
| 80 | +before merging in a pull request. |
| 81 | + |
| 82 | +[git-aliases]: https://github.com/willnorris/dotfiles/blob/d640d010c23b1116bdb3d4dc12088ed26120d87d/git/.gitconfig#L13-L15 |
| 83 | +[rebase-comment]: https://github.com/google/go-github/pull/277#issuecomment-183035491 |
| 84 | +[modified-comment]: https://github.com/google/go-github/pull/280#issuecomment-184859046 |
0 commit comments