-
Notifications
You must be signed in to change notification settings - Fork 11
CLOUDP-295785 - GitHub Actions workflow that checks for changelogs #263
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
base: maciejk/ar-versioning
Are you sure you want to change the base?
Conversation
818f617
to
a81ee10
Compare
8eed26e
to
63dd721
Compare
222a674
to
f35fa90
Compare
f35fa90
to
a8cedd0
Compare
c4067fb
to
d746a98
Compare
3866bc9
to
d6e789d
Compare
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 in general. Blocking just so that we double check that we do not expose secrets to malicious PRs.
6389b26
to
d956a13
Compare
5c5789d
to
0c494e0
Compare
MCK 1.3.0 Release NotesOther Changes
|
0c494e0
to
0286ddf
Compare
Changelog files are placed in the `changelog/` directory and used to generate the Release Notes for the | ||
upcoming release. Preview of the Release Notes is automatically added as comment to each Pull Request. |
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.
How do we generate release notes after looking at the change log? I am sorry if it's already documented somewhere and I don't remember.
Or in other words, do we polish/rephrase the changelog to make it release note or just use the change log as release note?
- [ ] Have you added changelog file? | ||
- use `skip-changelog` label if not needed | ||
- refer | ||
to [Changelog files and Release Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes) | ||
section in CONTRIBUTING.md for more details |
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.
Raising a PR and then for every PR adding skip-changelog
seems counter intuitive to me. Do we generally require all PRs to have change logs?
I think I am a little unsure about our definition of changelog and release note. If you can clarify that, maybe my question would be answered.
- name: Update PR comment | ||
# If the PR is from a fork, we cannot update the comment using read only permissions | ||
if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository | ||
run: gh issue comment $ISSUE --edit-last --create-if-none --body-file release_notes_preview.md | ||
env: | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
ISSUE: ${{ github.event.pull_request.html_url }} |
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.
I was just thinking how useful this comment is going to be. The rich preview of the .md files can easily be seen using github UI right?
That release note comment would just notify the reviewers I think.
Summary
This pull request introduces workflows to automate the validation and generation of release notes. It includes new script
scripts/release/check_changelog.py
for validating changelog file in PRs, created GitHub Actions workflow that calls validation script and another one to create release notes preview.GitHub Actions Workflows
.github/workflows/preview_release_notes.yml
to generate and preview release notes for pull requests and pushes tomaster
andrelease-*
branches..github/workflows/require_changelog.yml
to validate the inclusion of changelog entries in pull requests. The requirement can be skipped by labelling PR withskip-changelog
. Underneath the workflow usesscripts/release/check_changelog.py
script..github/actions/setup-ubuntu-host/action.yml
to set up an Ubuntu runner with Python and necessary dependencies for workflows.Proof of Work
Changelog requirement validation
When changelog exists -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16319921866/attempts/1#summary-46094783625
When changelog does not exist -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322098714/attempts/1#summary-46102343972
When changelog does not exist and the
skip-changelog
label was added -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322136466/attempts/1#summary-46102478174Release notes generation
Comment with Release Notes preview -> #263 (comment). GHA job summary -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322098704/attempts/1#summary-46102343937
Checklist
Reminder (Please remove this when merging)