Skip to content

Conversation

phillipj
Copy link
Member

Instead of reading the labelling config from the target branch/SHA, which for the nodejs/node project might be a staging branch.

As observed by @targos, always having to cherry-pick labelling config changes merged to the master branch, into different staging branches is very inconvenient and will be forgotten from time to time.

Let's instead always read the labelling config from the master branch.

Refs nodejs/node#38301 (comment)

/cc @nodejs/github-bot

Instead of reading the labelling config from the target branch/SHA,
which for the nodejs/node project might be a staging branch.

Always having to cherry-pick labelling config changes merged to the
master branch, into different staging branches is very inconvenient
and will be forgotten from time to time.
@phillipj phillipj merged commit fe83a8b into main Apr 26, 2021
@phillipj phillipj deleted the always-config-from-master branch April 26, 2021 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants