|
| 1 | +# Maintaining |
| 2 | + |
| 3 | +<!-- START doctoc generated TOC please keep comment here to allow auto update --> |
| 4 | +<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> |
| 5 | + |
| 6 | +**Table of Contents** |
| 7 | + |
| 8 | +- [Code of Conduct](#code-of-conduct) |
| 9 | +- [Issues](#issues) |
| 10 | +- [Pull Requests](#pull-requests) |
| 11 | +- [Release](#release) |
| 12 | +- [Thanks!](#thanks) |
| 13 | + |
| 14 | +<!-- END doctoc generated TOC please keep comment here to allow auto update --> |
| 15 | + |
| 16 | +This is documentation for maintainers of this project. |
| 17 | + |
| 18 | +## Code of Conduct |
| 19 | + |
| 20 | +Please review, understand, and be an example of it. Violations of the code of conduct are taken |
| 21 | +seriously, even (especially) for maintainers. |
| 22 | + |
| 23 | +## Issues |
| 24 | + |
| 25 | +We want to support and build the community. We do that best by helping people learn to solve their |
| 26 | +own problems. We have an issue template and hopefully most folks follow it. If it's not clear what |
| 27 | +the issue is, invite them to create a minimal reproduction of what they're trying to accomplish or |
| 28 | +the bug they think they've found. |
| 29 | + |
| 30 | +Once it's determined that a code change is necessary, point people to |
| 31 | +[makeapullrequest.com](https://makeapullrequest.com) and invite them to make a pull request. If |
| 32 | +they're the one who needs the feature, they're the one who can build it. If they need some hand |
| 33 | +holding and you have time to lend a hand, please do so. It's an investment into another human being, |
| 34 | +and an investment into a potential maintainer. |
| 35 | + |
| 36 | +Remember that this is open source, so the code is not yours, it's ours. If someone needs a change in |
| 37 | +the codebase, you don't have to make it happen yourself. Commit as much time to the project as you |
| 38 | +want/need to. Nobody can ask any more of you than that. |
| 39 | + |
| 40 | +## Pull Requests |
| 41 | + |
| 42 | +As a maintainer, you're fine to make your branches on the main repo or on your own fork. Either way |
| 43 | +is fine. |
| 44 | + |
| 45 | +When we receive a pull request, a GitHub Action is kicked off automatically (see the |
| 46 | +`.github/workflows/validate.yml` for what runs in the Action). We avoid merging anything that breaks |
| 47 | +the GitHub Action. |
| 48 | + |
| 49 | +Please review PRs and focus on the code rather than the individual. You never know when this is |
| 50 | +someone's first ever PR and we want their experience to be as positive as possible, so be uplifting |
| 51 | +and constructive. |
| 52 | + |
| 53 | +When you merge the pull request, 99% of the time you should use the |
| 54 | +[Squash and merge](https://help.github.com/articles/merging-a-pull-request/) feature. This keeps our |
| 55 | +git history clean, but more importantly, this allows us to make any necessary changes to the commit |
| 56 | +message so we release what we want to release. See the next section on Releases for more about that. |
| 57 | + |
| 58 | +## Release |
| 59 | + |
| 60 | +Our releases are automatic. They happen whenever code lands into `main`. A GitHub Action gets kicked |
| 61 | +off and if it's successful, a tool called |
| 62 | +[`semantic-release`](https://github.com/semantic-release/semantic-release) is used to automatically |
| 63 | +publish a new release to npm as well as a changelog to GitHub. It is only able to determine the |
| 64 | +version and whether a release is necessary by the git commit messages. With this in mind, **please |
| 65 | +brush up on [the commit message convention][commit] which drives our releases.** |
| 66 | + |
| 67 | +> One important note about this: Please make sure that commit messages do NOT contain the words |
| 68 | +> "BREAKING CHANGE" in them unless we want to push a major version. I've been burned by this more |
| 69 | +> than once where someone will include "BREAKING CHANGE: None" and it will end up releasing a new |
| 70 | +> major version. Not a huge deal honestly, but kind of annoying... |
| 71 | +
|
| 72 | +## Thanks! |
| 73 | + |
| 74 | +Thank you so much for helping to maintain this project! |
| 75 | + |
| 76 | +<!-- prettier-ignore-start --> |
| 77 | +[commit]: https://github.com/conventional-changelog-archived-repos/conventional-changelog-angular/blob/ed32559941719a130bb0327f886d6a32a8cbc2ba/convention.md |
| 78 | +<!-- prettier-ignore-end --> |
0 commit comments