Skip to content
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 to assert changelog updates #2675

Merged
merged 10 commits into from
May 25, 2024
Merged

Conversation

carsakiller
Copy link
Collaborator

@carsakiller carsakiller commented May 23, 2024

This PR adds a workflow that checks incoming PRs for changelog changes, failing if no changes were made.

Another important change is that the changelog should always contain an “Unreleased” section at the top, so it is easy to add all new changes there between releases. When it is time for a new release, the points from under “Unreleased” are simply moved under a version number.

This should help prevent new changes from going under the radar.

@sumneko I have also edited the branch protection rules on master so that in order for a pull request to be merged, this changelog edit check must succeed before merging, although admins can still override it and merge regardless.

@carsakiller carsakiller added the documentation Has to do with documentation either in the wiki or in the repo label May 23, 2024
@carsakiller
Copy link
Collaborator Author

GitHub's documentation on what values are available in a pull request workflow is not the greatest. I'm not sure if it now only works for pushes to pull requests and will always fail upon the first opening of a pull request… but I won't know until it fails. I would not be surprised if this false-fails on the next PR, but just @ me, and I'll take a look 🙂

@carsakiller carsakiller marked this pull request as ready for review May 23, 2024 08:40
@sumneko sumneko merged commit b79a668 into LuaLS:master May 25, 2024
11 checks passed
@carsakiller carsakiller deleted the log-changes branch May 25, 2024 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Has to do with documentation either in the wiki or in the repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants