housekeeping: ignore cla github labels otherwise release will break #1430
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ghuntley, |
|
Changes Unknown when pulling 8e3ecbc on ignore-dotnet-foundaiton-labels into ** on develop**. |
ghuntley
added a commit
that referenced
this pull request
Nov 6, 2017
glennawatson
pushed a commit
that referenced
this pull request
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
housekeeping
What is the current behavior? (You can also link to an open issue here)
DNF labels would cause GRM to fail/we would not be able to release.
What is the new behavior (if this is a feature change)?
Ignore all DNF labels
What might this PR break?
This will unbreak the release of v8.0.0; haven't discovered this yet because no releases have been done since joining the .NET foundation. GRM has a limitation (GitTools/GitReleaseManager#90) where an issue can only belong to one label.
Please check if the PR fulfills these requirements
Other information: