tools: fix release proposal linter to support more than 1 folk preparing#56203
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Dec 12, 2024
Merged
tools: fix release proposal linter to support more than 1 folk preparing#56203nodejs-github-bot merged 1 commit intonodejs:mainfrom
nodejs-github-bot merged 1 commit intonodejs:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the person preparing the release is not the person promoting it, there are more than 1
@char and the linter should account for that.in this case, it's a matter of using
%%instead of%bash parameter expansion. I'm also changing the test syntax to align with how our.shfiles linter is set even though it's not running on shell script written inside YAML files.