Factor issue and edit MR form label and submit. #7802
Merged
Conversation
This file contains 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
|
I've prepared a stage. Click to open. |
cirosantilli
changed the title
cirosantilli
force-pushed
the
factor-issue-mr-form-label
branch
from
bd9b411
to
4084896
Compare
cirosantilli
changed the title
cirosantilli
force-pushed
the
factor-issue-mr-form-label
branch
4 times, most recently
from
b7a1d01
to
77d38ac
Compare
|
@cirosantilli Can you rebase? |
cirosantilli
force-pushed
the
factor-issue-mr-form-label
branch
from
77d38ac
to
705fe01
Compare
|
Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a direct continuation of: #7678
I had left it out because they were harder to factor, but I think I've manged now.
There should be no UI changes.
Implementation notes:
link_to [issuable.project, issuable]is magic and redirects to either index or show depending on ifissuablealready exists or not.issuable.new_record?is never reached for the Merge request because the new issue and new MR have diverged... but let's leave that in place for when we merge them together.