fix: update GitLab merge request prefix to '!' #8227
Merged
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
Change the prefix for GitLab merge requests from '#' to '!' in the PullRequestCard component to correctly reflect markdown syntax.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@nolith is attempting to deploy a commit to the GitButler Team on Vercel. A member of the Team first needs to authorize it. |
|
@estib-vega this should close #8210 on top of your work, do you mind taking a look? 🙏 |
|
@nolith oh dumb mistake of mine. Nice catch! |
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.
Change the prefix for GitLab merge requests from '#' to '!' in the PullRequestCard component to correctly reflect markdown syntax.
🧢 Changes
In #8221 the ability to distinguish UI elements by forge was introduced, but the correct MR symbol for GitLab is
!.☕️ Reasoning
If this PR is related to a specific issue, uncomment this section
and link it via the following text:
🎫 Affected issues
Fixes: #8210