-
Notifications
You must be signed in to change notification settings - Fork 235
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
[FEA] changelog generator #599
Conversation
build |
1 similar comment
build |
|
||
e.g. | ||
cd spark-rapids/ | ||
.github/workflows/changelog/changelog --token=<GITHUB_PERSONAL_ACCESS_TOKEN> --base_refs=branch-0.1,branch-0.2,branch-0.3 |
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.
might be nice to add change_log is generated for each of the the branches specified.
I assume the assumption here is that we only do 1 release on each branch?
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.
Yes we are making the assumption that we do one release per branch.
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.
@tgravescs yes, plz take a look at the CHANGELOG.md, this is the rendered markdown preview. Since we separate prs&issues by the release info (github projects
), so I try to map the pr&issue back to projects info. And plz let me know if anything else you want
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.
my comment was saying we should update the description of this script to tell user what base_ref really does.
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.
@tgravescs sure thing. I will add a detailed description in upcoming commits
7cb34ff
to
c84ea42
Compare
build |
2 similar comments
build |
build |
98e8758
to
2f4f3c4
Compare
build |
so I added detailed desc in the script. Also there is nan auto-doc-gen workflow within this PR, so the workflow will be triggered each time a PR got merged and create a |
Please, let's not double the number of PRs. IMO we only need a changelog when we release, so we only need to run the changelog generator as part of the release process. |
Can we generate the CHANGELOG.md and auto-merge without doing a build? That way we could generate on some regular cadence (nightly?). |
I am not a fan of this approach. The changelog results are highly sensitive to proper labeling and assigning to projects in github, and as the first cut showed, this is far from perfect. We need a tool to generate a changelog in preparation for a release, and I believe that changelog is going to need someone to review it for accuracy. Automerging the tool's output without review is asking for trouble like saying some issue is fixed in the release when it was instead closed as won't fix, etc. |
@jlowe @sameerz actually unlike automerge, the changelog workflow won't merge the PR by itself, and it will keep just one opened doc-gen PR for review, new updates will be committed to the same PR. So team-reviews will be responsible to review the auto-gen doc and merge the PR. cudf ask to submit PR with changelog update in their commit, but I am also agree with that we could generate the change log when we really do the release. |
2f4f3c4
to
0733122
Compare
build |
so I just pushed commits to disable the workflow by |
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.
we could easily turn this on if things changed in the future
I personally would never want to double our commit load and clutter our commit history with a bunch of changelog-only PRs. If for some reason we need a changelog update on every PR merged, I'd rather see a hook that does the changelog update as part of the PR commit rather than a separate PR that's auto-merged. It's simply a lot less traffic and noise. In that scenario we're not doing a full changelog generation but a targeted changelog edit which is a very different workflow and script.
This looks OK to me other than I don't think we'll ever use the workflow setup, so I'm dubious on the utility of checking in dead code. Also it's a bit odd to "hide" the script we expect someone to manually run as part of building the release in the .github/workflows
directory. I'd rather see this script under a top-level dev/
or scripts/
directory (or maybe even next to the documentation on how to release which should be under the docs/dev/
directory), but that's not a blocker for me. Curious what others think.
ffc4ac3
to
bd7cfe9
Compare
build |
Ok, I removed the workflow-related code and move the script to the We could add a post-commit hook in the future if someone really need some automation 👍 |
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.
Can the name of this script be changed to something like generate-changelog
? Otherwise it looks like it could be a changelog document for the scripts directory.
build |
Signed-off-by: Peixin Li <[email protected]>
build |
d29c536
to
e0b5cc1
Compare
build |
1 similar comment
build |
* changelog generator Signed-off-by: Peixin Li <[email protected]>
* changelog generator Signed-off-by: Peixin Li <[email protected]>
[auto-merge] bot-auto-merge-branch-22.10 to branch-22.12 [skip ci] [bot]
fix #573
Generated CHANGELOG.md
example stdout: