You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When some files in a plugin are changed for the first time, the version numbers need to be bumped in the META-INF/MANIFEST.MF (and potentially pom.xml) files.
Something similar is done to tell users when their PR has merge commits.
However, these actions won't be executed for PRs written by first-time contributors to a repository until a committer approves them (and I'd argue that especially the check for merge commits is pretty relevant for first-time contributors).
Because of that, I suggest changing the approval setting for GitHub actions to "Require approval for first-time contributors who are new to GitHub" in most repositories using that action (Settings > Actions > General > Approval for running fork pull request workflows from contributors) - at least in projects where the committers/project leads want that.
I don't think allowing anyone to use GitHub Actions would be much of an issue because anyone who fixed a typo or similar can already do that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When some files in a plugin are changed for the first time, the version numbers need to be bumped in the
META-INF/MANIFEST.MF
(and potentiallypom.xml
) files.To make this less annoying, GitHub Actions automatically updates the PR with the version bump and adds a comment.

Something similar is done to tell users when their PR has merge commits.
However, these actions won't be executed for PRs written by first-time contributors to a repository until a committer approves them (and I'd argue that especially the check for merge commits is pretty relevant for first-time contributors).
Because of that, I suggest changing the approval setting for GitHub actions to "Require approval for first-time contributors who are new to GitHub" in most repositories using that action (Settings > Actions > General > Approval for running fork pull request workflows from contributors) - at least in projects where the committers/project leads want that.

I don't think allowing anyone to use GitHub Actions would be much of an issue because anyone who fixed a typo or similar can already do that.
Beta Was this translation helpful? Give feedback.
All reactions