Skip merge requests in given states#118
Merged
spruce merged 2 commits intopiceaTech:masterfrom Jan 10, 2022
Merged
Conversation
Member
|
Wouldn't this lead to the issue numbers diverging from github and gitlab? |
Contributor
Author
|
AFAIK merge requests are numbered independently from issues in GitLab, but not in GitHub, where everything is an issue, so this shouldn't be a problem. It could mess things up if #121 is implemented as suggested there. In that case maybe one could create and delete issues instead. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR adds a new config variable
skipMergeRequestStateswhich is an array of strings. Merge requests with a state listed in this array will not be migrated. Closes #105