Skip to content

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

Merged
merged 2 commits into from
Jan 19, 2023

Conversation

mafredri
Copy link
Member

@mafredri mafredri commented Jan 11, 2023

This PR adds documentation to CONTRIBUTING.md for creating releases and how to write commits.

It also improves the --help of release.sh.

Fixes #5233
Fixes #5380

@mafredri mafredri self-assigned this Jan 11, 2023
@mafredri mafredri requested a review from bpmct January 11, 2023 18:24
Copy link
Member

@bpmct bpmct left a 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/).
Copy link
Member

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.

Copy link
Member Author

@mafredri mafredri Jan 12, 2023

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 😄

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM!

@mtojek mtojek self-requested a review January 13, 2023 09:02
@mafredri mafredri force-pushed the mafredri/docs-release branch from 989ac12 to 1d64aaf Compare January 17, 2023 14:16
@mafredri mafredri merged commit 1f3b7b6 into main Jan 19, 2023
@mafredri mafredri deleted the mafredri/docs-release branch January 19, 2023 13:13
@github-actions github-actions bot locked and limited conversation to collaborators Jan 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore: document release/commit titles improve release workflow to detect breaking changes
3 participants