-
Notifications
You must be signed in to change notification settings - Fork 5
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
Document release notes procedure #1705
Open
GitHK
wants to merge
32
commits into
master
Choose a base branch
from
document-release-notes-procedure
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GitHK
requested review from
giancarloromeo,
jsaq007,
ignapas,
mrnicegyu11,
pcrespov,
odeimaiz,
mguidon,
sanderegg,
YuryHrytsuk,
JavierGOrdonnez and
matusdrobuliak66
September 17, 2024 14:41
pcrespov
reviewed
Sep 17, 2024
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.
thx
- please pass a spellchecker to the readme (and in general all the texts that you are also generating with the scripts) :-)
- IMO some of the scripts (generating more instructions) are unnecessary, but ok :-)
- i find the workflow a bit too manual which IMO reduces the changes to succeed ...
pcrespov
reviewed
Sep 17, 2024
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.
👍
sanderegg
reviewed
Sep 17, 2024
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.
ok, thanks
matusdrobuliak66
approved these changes
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds documentation how to handle the release notes.
It is important that the procedure is written down, since it's the scrum master's responsibility to enforce it.
This also makes it easier to update.
I have tried to create as much automation as possible in order to aid the scrum master.
Bonus:
.pre-commit-config.yaml
configscripts
scripts
TODOs:
Related issues: