-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add workflow for changelog verification #4085
Add workflow for changelog verification #4085
Conversation
Signed-off-by: Kunal Kotwani <kkotwani@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
|
Gradle Check (Jenkins) Run Completed with:
|
name: "Changelog Verifier" | ||
on: | ||
pull_request: | ||
types: [opened, synchronize, reopened, ready_for_review, labeled, unlabeled] |
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.
Why not all PRs?
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.
The default mechanism for pull_request
trigger is as follows:
By default, a workflow only runs when a pull_request event's activity type is opened, synchronize, or reopened.
I have updated the GHA config to reflect all the types I found could match our case.
CHANGELOG.md
Outdated
|
||
## [ UNRELEASED ] | ||
### Added | ||
- Github workflow for changelog verification |
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.
Let's start with a format that includes a link to the PR?
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.
The only concern I have with that is it will become a 2 step process -
- Add changelog with dummy link and raise the PR
- Update the changelog and commit again with the PR link
Let me check if there is an automated mechanism/property within the used GHA to achieve this.
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.
Working backwards from the end goal of users being able to find what the change was I think that's an acceptable overhead.
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 love it. Super simple. Let's update developer docs too?
Yes. I will update the PR as soon as we have the syntax and process finalized. |
fc2879a
to
fb9d28e
Compare
Signed-off-by: Kunal Kotwani <kkotwani@amazon.com>
fb9d28e
to
f8986a9
Compare
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
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 like the idea of being able to enforce this in an automated way so that it isn't forgotten!
CONTRIBUTING.md
Outdated
## [ UNRELEASED ] | ||
### Added | ||
- ... | ||
- Add support for FooBar client ([#9999](https://github.com/opensearch-project/OpenSearch/pull/9999)) |
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.
Is it possible to change the format to include the contributor alias? I want to give people easy credit for the work they do.
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.
as i already wrote in opensearch-project/security#1821 (comment) i personally don't think listing the contributors is a good idea. when reading the changelog i want to know what changed and what it means for me - any other information is just annoying clutter and will be ignored and slows me down. i can always follow the links or check the commit history to know more.
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 potentially use github aliases within the format, but like the PRs, it would be a self update process.
+1 on following the PR links / browsing commit history to reduce information overload.
Signed-off-by: Kunal Kotwani <kkotwani@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle check:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Unrelated:
|
Gradle Check (Jenkins) Run Completed with:
|
CONTRIBUTING.md
Outdated
|
||
For example, as a contributor, my change adds support for a new `FooBar` client, the changes would look like - | ||
|
||
``` |
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.
tbh, i don't really see the value in duplicating the content of a near-empty CHANGELOG.md
here again. why not just write
``` | |
2. Add an entry for your change to the corresponding section in [`CHANGELOG.md`](CHANGELOG.md) and make sure that you reference the pull request there. |
or, if you truly want to keep it, at least turn it into markdown syntax highlighting:
``` | |
```md |
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.
Updated the PR!
Signed-off-by: Kunal Kotwani <kkotwani@amazon.com>
…OpenSearch into changelog-verifier
Signed-off-by: Kunal Kotwani <kkotwani@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
I merged it. Let's backport to 2.x and try to run with this. |
* Add workflow for changelog verification Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update format for changelog, add developer documentation Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update link reference to be relative to project Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Fix links for CHANGELOG versions Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update contribution guide Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> (cherry picked from commit 5327767)
* Add workflow for changelog verification Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update format for changelog, add developer documentation Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update link reference to be relative to project Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Fix links for CHANGELOG versions Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update contribution guide Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> (cherry picked from commit 5327767) Co-authored-by: Kunal Kotwani <kkotwani@amazon.com>
@kotwanikunal Are you going to take this on as a campaign for all plugins once it's stable here? Maybe we need to open sub-issues in those repos? |
@dblock I can run that once we ensure the process and any further automation/guardrails are in place. |
* Add workflow for changelog verification Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update format for changelog, add developer documentation Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update link reference to be relative to project Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Fix links for CHANGELOG versions Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update contribution guide Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> (cherry picked from commit 5327767)
* Add workflow for changelog verification Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update format for changelog, add developer documentation Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update link reference to be relative to project Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Fix links for CHANGELOG versions Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> * Update contribution guide Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> Signed-off-by: Kunal Kotwani <kkotwani@amazon.com> (cherry picked from commit 5327767) Co-authored-by: Kunal Kotwani <kkotwani@amazon.com>
@kotwanikunal @dblock I think the changelog doc link in the checklist section is broken. I recently opened this PR #4360 and you can see that the link points to https://github.com/opensearch-project/OpenSearch/CONTRIBUTING.md#changelog which is wrong. Correct link is https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#changelog. Maybe we need to change the relative link from |
I'll add in the fix. Thanks for bringing it to notice. |
@lukas-vlcek Fixed it with #4364 |
Signed-off-by: Kunal Kotwani kkotwani@amazon.com
Description
Changelog Enforcer
following the Keep A Changelog formatCHANGELOG.md
fileIssues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.