-
Notifications
You must be signed in to change notification settings - Fork 886
docs: Add documentation for releases and commit style #5675
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
Conversation
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.
This reads very well. Thanks for documenting this!
- Good: `feat(api): Add feature X` | ||
- Bad: `feat(api): Added feature X` (past tense) | ||
|
||
A good rule of thumb for writing good commit messages is to recite: [If applied, this commit will ...](https://reflectoring.io/meaningful-commit-messages/). |
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.
When I merge PRs, I make sure that the first line of commit message is aligned with the convention. Should I also pay attention to other lines? For instance:
commit d9436fab69203740a25c29f2d27146bb04bc14c3 (upstream/main, main)
Author: Marcin Tojek <mtojek@users.noreply.github.com>
Date: Wed Jan 11 16:05:42 2023 +0100
docs: API enterprise (#5625)
* docs: audit, deploymentconfig, files, parameters
* Swagger comments in workspacebuilds.go
* structs in workspacebuilds.go
* workspaceagents: instance identity
* workspaceagents.go in progress
* workspaceagents.go in progress
* Agents
* workspacebuilds.go
...
I know that this can really long.
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.
Great question. I haven’t given it much thought to what it should look like.
Personally I usually either remove the bullets entirely, rewrite it as proper paragraphs (max width 72) or only keep/rewrite certain relevant bullet points.
Using the type/prefix is not necessary for these IMO. But it’s also not a crime to use them 😄
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.
SGTM!
989ac12
to
1d64aaf
Compare
This PR adds documentation to
CONTRIBUTING.md
for creating releases and how to write commits.It also improves the
--help
ofrelease.sh
.Fixes #5233
Fixes #5380