-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Minor changes to contributing doc and pr template for conventional commits #12439
Conversation
commits. Signed-off-by: Callum Styan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team] two small tweaks, otherwise LGTM.
CONTRIBUTING.md
Outdated
1. Your PR documents upgrading steps under `docs/sources/setup/upgrade/_index.md` if it changes: | ||
1. It starts with an imperative verb. Example: Fix the latency between System A and System B. | ||
2. It uses Sentence case, not Title Case. | ||
3. It has a clear description saying what it does and why. Your PR description will be present in the project' commit log, so be gentle to it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming that random apostrophe was meant to be a possessive?
3. It has a clear description saying what it does and why. Your PR description will be present in the project' commit log, so be gentle to it. | |
3. It has a clear description saying what it does and why. Your PR description will be present in the project's commit log, so be gentle to it. |
CONTRIBUTING.md
Outdated
1. It starts with an imperative verb. Example: Fix the latency between System A and System B. | ||
2. It uses Sentence case, not Title Case. | ||
3. It has a clear description saying what it does and why. Your PR description will be present in the project' commit log, so be gentle to it. | ||
2. Your PR is well sync'ed with main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Your PR is well sync'ed with main | |
2. Your PR is well synched with main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but let's also remove the GH workflow that was acting on that add-to-release-notes
label with this PR as well
@@ -9,8 +9,7 @@ Fixes #<issue number> | |||
- [ ] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) | |||
- [ ] Documentation added | |||
- [ ] Tests updated | |||
- [ ] `CHANGELOG.md` updated | |||
- [ ] If the change is worth mentioning in the release notes, add `add-to-release-notes` label |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why don't we remove the action that was updating the release notes with this PR as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, I also added a note that we need to update the docs about updating the release notes as well, I'm not sure what changes we need to make there at the moment
Signed-off-by: Callum Styan <[email protected]>
…onal commits (grafana#12439) Signed-off-by: Callum Styan <[email protected]>
Changes based on the fact that we're now using conventional commits, we no longer want contributors making changes to the changelog themselves + we should include the link to conventional commits doc in the PR template.