Branch name must be URL encoded

Hey @GeorgesZ473!

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help moving the MR forward, feel free to post @gitlab-bot help. Read more on how to get help.

To enable automated checks on your MR, please configure Danger for your fork.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @GeorgesZ473

added 1st contribution label

@gitlab-bot ready

added workflowready for review label and removed workflowin dev label

Hi @phillipwells! Please review this documentation merge request. This message was generated automatically. You're welcome to improve it.

added documentation twtriaged labels

requested review from @phillipwells

@phillipwells, this Community contribution is ready for review.

Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
Add the workflowin dev label if the merge request needs action from the author. This message was generated automatically. You're welcome to improve it.

changed the description

mentioned in issue gitlab-org/quality/triage-reports#9495 (closed)

mentioned in issue gitlab-org/quality/triage-reports#9512 (closed)

added typemaintenance label

added 1 deleted label

changed milestone to %15.5

removed 1 deleted label

added Technical Writing devopscreate docsimprovement groupsource code labels

added sectiondev label

Thanks for your contribution, @GeorgesZ473! The change looks good to me, but I'll tag in an engineer to make sure I'm not missing anything.

@ghinfey could you confirm that this docs change makes sense? Thanks!

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

doc/api/branches.md

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

removed workflowready for review label

resolved all threads

approved this merge request

added maintenancerefactor label

enabled an automatic merge when the pipeline for 6d1f6a7e succeeds

merged

@GeorgesZ473, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

Leave a or a on this comment to describe your experience.
Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help!

This message was generated automatically. You're welcome to improve it.