GitLab quick actions | GitLab (2023)

  • Parameters
  • Issues, merge requests, and epics
  • Commit messages

Version history

  • Introduced in GitLab 12.1:once an action is executed, an alert appears when a quick action is successfully applied.
  • Introduced in GitLab 13.2: you can usequick actions when updating the description of issues, epics, and merge requests.
  • Introduced in GitLab 13.8: when you enter/ into a description or comment field, all available quick actions are displayed in a scrollable list.
  • The rebase quick action was introduced in GitLab 13.8.
(Video) GitLab DevOps Platform 5 min Demo

Quick actions are text-based shortcuts for common actions that are usually doneby selecting buttons or dropdowns in the GitLab user interface. You can enterthese commands in the descriptions or comments of issues, epics, merge requests,and commits.

Many quick actions are context-aware, requiring certain conditions be met. For example, to removean issue due date with /remove_due_date, the issue must have a due date set.

Be sure to enter each quick action on a separate line to allow GitLab toproperly detect and execute the commands.

(Video) What is GitLab? Speed. Efficiency. Trust.


Many quick actions require a parameter. For example, the /assign quick actionrequires a username. GitLab uses autocomplete characterswith quick actions to help users enter parameters, by providing a list ofavailable values.

If you manually enter a parameter, it must be enclosed in double quotation marks("), unless it contains only these characters:

  • ASCII letters
  • Numbers (0-9)
  • Underscore (_), hyphen (-), question mark (?), dot (.), ampersand (&) or at (@)

Parameters are case-sensitive. Autocomplete handles this, and the insertionof quotation marks, automatically.

(Video) Learn GitLab in 3 Hours | GitLab Complete Tutorial For Beginners

Issues, merge requests, and epics

The following quick actions are applicable to descriptions, discussions, andthreads. Some quick actions might not be available to all subscription tiers.

CommandIssueMerge requestEpicAction
/add_contacts [] [] Yes No NoAdd one or more CRM contacts (introduced in GitLab 14.6).
/approve No Yes NoApprove the merge request.
/assign @user1 @user2 Yes Yes NoAssign one or more users.
/assign me Yes Yes NoAssign yourself.
/assign_reviewer @user1 @user2 or /reviewer @user1 @user2 or /request_review @user1 @user2 No Yes NoAssign one or more users as reviewers.
/assign_reviewer me or /reviewer me or /request_review me No Yes NoAssign yourself as a reviewer.
/award :emoji: Yes Yes YesToggle emoji award.
/cc @user Yes Yes YesMention a user. In GitLab 15.0 and later, this command performs no action. You can instead type CC @user or only @user. In GitLab 14.9 and earlier, mentioning a user at the start of a line created a specific type of to-do item notification.
/child_epic <epic> No No YesAdd child epic to <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic (introduced in GitLab 12.0).
/clear_health_status Yes No NoClear health status (introduced in GitLab 14.7).
/clear_weight Yes No NoClear weight.
/clone <path/to/project> [--with_notes] Yes No NoClone the issue to given project, or the current one if no arguments are given (introduced in GitLab 13.7). Copies as much data as possible as long as the target project contains equivalent labels, milestones, and so on. Does not copy comments or system notes unless --with_notes is provided as an argument.
/close Yes Yes YesClose.
/confidential Yes No NoMake confidential.
/copy_metadata <!merge_request> Yes Yes NoCopy labels and milestone from another merge request in the project.
/copy_metadata <#issue> Yes Yes NoCopy labels and milestone from another issue in the project.
/create_merge_request <branch name> Yes No NoCreate a new merge request starting from the current issue.
/done Yes Yes YesMark to do as done.
/draft No Yes NoSet the draft status. Use for toggling the draft status (deprecated in GitLab 15.4.)
/due <date> Yes No NoSet due date. Examples of valid <date> include in 2 days, this Friday and December 31st.
/duplicate <#issue> Yes No NoClose this issue and mark as a duplicate of another issue. Also, mark both as related.
/epic <epic> Yes No NoAdd to epic <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic.
/estimate <time> Yes Yes NoSet time estimate. For example, /estimate 1mo 2w 3d 4h 5m. Learn more about time tracking.
/health_status <value> Yes No NoSet health status. Valid options for <value> are on_track, needs_attention, and at_risk (introduced in GitLab 14.7).
/invite_email email1 email2 Yes No NoAdd up to six email participants. This action is behind feature flag issue_email_participants and is not yet supported in issue templates.
/iteration *iteration:"iteration name" Yes No NoSet iteration. For example, to set the Late in July iteration: /iteration *iteration:"Late in July" (introduced in GitLab 13.1).
/label ~label1 ~label2 Yes Yes YesAdd one or more labels. Label names can also start without a tilde (~), but mixed syntax is not supported.
/lock Yes Yes NoLock the discussions.
/merge No Yes NoMerge changes. Depending on the project setting, this may be when the pipeline succeeds, or adding to a Merge Train.
/milestone %milestone Yes Yes NoSet milestone.
/move <path/to/project> Yes No NoMove this issue to another project. Be careful when moving an issue to a project with different access rules. Before moving the issue, make sure it does not contain sensitive data.
/parent_epic <epic> No No YesSet parent epic to <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic (introduced in GitLab 12.1).
/promote Yes No NoPromote issue to epic.
/promote_to_incident Yes No NoPromote issue to incident (introduced in GitLab 14.5).
/page <policy name> Yes No NoStart escalations for the incident (introduced in GitLab 14.9).
/publish Yes No NoPublish issue to an associated Status Page (Introduced in GitLab 13.0)
/ready No Yes NoSet the ready status (Introduced in GitLab 15.1).
/reassign @user1 @user2 Yes Yes NoReplace current assignees with those specified.
/reassign_reviewer @user1 @user2 No Yes NoReplace current reviewers with those specified.
/rebase No Yes NoRebase source branch. This schedules a background task that attempts to rebase the changes in the source branch on the latest commit of the target branch. If /rebase is used, /merge is ignored to avoid a race condition where the source branch is merged or deleted before it is rebased. If there are merge conflicts, GitLab displays a message that a rebase cannot be scheduled. Rebase failures are displayed with the merge request status.
/relabel ~label1 ~label2 Yes Yes YesReplace current labels with those specified.
/relate #issue1 #issue2 Yes No NoMark issues as related.
/remove_child_epic <epic> No No YesRemove child epic from <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic (introduced in GitLab 12.0).
/remove_contacts [] [] Yes No NoRemove one or more CRM contacts (introduced in GitLab 14.6).
/remove_due_date Yes No NoRemove due date.
/remove_epic Yes No NoRemove from epic.
/remove_estimate Yes Yes NoRemove time estimate.
/remove_iteration Yes No NoRemove iteration (introduced in GitLab 13.1).
/remove_milestone Yes Yes NoRemove milestone.
/remove_parent_epic No No YesRemove parent epic from epic (introduced in GitLab 12.1).
/remove_time_spent Yes Yes NoRemove time spent.
/remove_zoom Yes No NoRemove Zoom meeting from this issue.
/reopen Yes Yes YesReopen.
/severity <severity> Yes No NoSet the severity. Issue type must be Incident. Options for <severity> are S1S4, critical, high, medium, low, unknown. Introduced in GitLab 14.2.
/shrug <comment> Yes Yes YesAppend the comment with ¯\_(ツ)_/¯.
/spend <time> [<date>] Yes Yes NoAdd or subtract spent time. Optionally, specify the date that time was spent on. For example, /spend 1mo 2w 3d 4h 5m 2018-08-26 or /spend -1h 30m. Learn more about time tracking.
/submit_review No Yes NoSubmit a pending review (introduced in GitLab 12.7).
/subscribe Yes Yes YesSubscribe to notifications.
/tableflip <comment> Yes Yes YesAppend the comment with (╯°□°)╯︵ ┻━┻.
/target_branch <local branch name> No Yes NoSet target branch.
/title <new title> Yes Yes YesChange title.
/timeline <timeline comment> \| <date(YYYY-MM-DD)> <time(HH:MM)> Yes No NoAdd a timeline event to this incident. For example, /timeline DB load spiked \| 2022-09-07 09:30. (introduced in GitLab 15.4).
/todo Yes Yes YesAdd a to-do item.
/unapprove No Yes NoUnapprove the merge request. (introduced in GitLab 14.3
/unassign @user1 @user2 Yes Yes NoRemove specific assignees.
/unassign No Yes NoRemove all assignees.
/unassign_reviewer @user1 @user2 or /remove_reviewer @user1 @user2 No Yes NoRemove specific reviewers.
/unassign_reviewer me No Yes NoRemove yourself as a reviewer.
/unassign_reviewer or /remove_reviewer No Yes NoRemove all reviewers.
/unlabel ~label1 ~label2 or /remove_label ~label1 ~label2 Yes Yes YesRemove specified labels.
/unlabel or /remove_label Yes Yes YesRemove all labels.
/unlock Yes Yes NoUnlock the discussions.
/unsubscribe Yes Yes YesUnsubscribe from notifications.
/weight <value> Yes No NoSet weight. Valid options for <value> include 0, 1, 2, and so on.
/zoom <Zoom URL> Yes No NoAdd a Zoom meeting to this issue or incident. In GitLab 15.3 and later users on GitLab Premium can add a short description when adding a Zoom link to an incident.

Commit messages

The following quick actions are applicable for commit messages:

/tag v1.2.3 <message>Tags the commit with an optional message.
(Video) #6 Gitlab Quick Actions | Gitlab Tutorial For Absolute Beginners


What are GitLab quick actions? ›

GitLab quick actions

Quick actions are textual shortcuts for common actions on issues or merge requests that are usually done by clicking buttons or dropdowns in GitLab's UI. You can enter these commands while creating a new issue or merge request, and in comments.

How do I create a merge request template in GitLab? ›

Creating Merge Request Templates

md files within your project repository. Create a template in the . gitlab/merge_request_templates folder (you may need to create the folder first) and, once it is on your default branch, it will be available when creating new merge requests.

What is the use of quick action? ›

Quick actions enable users to do more in Salesforce and in the Salesforce mobile app. With custom quick actions, you can make your users' navigation and workflow as smooth as possible by giving them convenient access to information that's most important.

What is the use of quick action button? ›

Quick actions allow users to perform contextual actions when hovering or focusing on a specific component. They're shortcuts meant to make workflows more efficient.

Is merge request same as pull request? ›

A Git pull request is essentially the same as a Git merge request. Both requests achieve the same result: merging a developer's branch with the project's master or main branch. Their difference lies in which site they are used; GitHub uses the Git pull request, and GitLab uses the Git merge request.

Can you cherry-pick a merge request? ›

You can cherry-pick commits from any merge request in your project, regardless of whether the merge request is open or closed. To cherry-pick a commit from the list of commits included in a merge request: On the top bar, select Main menu > Projects and find your project.

Do pull requests automatically merge? ›

If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and all required status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.

Can we launch flow using quick action? ›

Help users launch and navigate through workflows with the help of quick actions. Quick actions enable you to perform a series of actions with just a few clicks. You can also create customized quick actions based on the specific needs of your users.

How can you custom quick actions? ›

How to Create a Global Action
  1. Go to Setup → User Interface → Global Actions → Global Actions. ...
  2. Select Action Type = 'Create a Record'. ...
  3. Click Success Message. ...
  4. Next, we'll add relevant fields that the user will need to complete to the layout. ...
  5. Let's set predefined values for Lead Status and Lead Source.
24 Jan 2022

Can we add quick action in related list? ›

In order to do any prepopulation of fields, it is suggested to use a quick action. If we have a related list object and we are trying to prepopulate the object of the related list, we would make a quick action and remove the "New" button.

What is an action button very short answer? ›

An action button is an object on a slide that performs an action when clicked or pointed to, such as jumping to another slide or playing a sound. Action buttons are most commonly used for self-running presentations—for example, presentations that are presented at a booth or kiosk.

What are the three uses of an action button? ›

Action buttons are built-in button shapes you can add to a presentation and set to link to another slide, play a sound, or perform a similar action. When someone clicks or moves over the button, the selected action will occur. Action buttons can do many of the same things as hyperlinks.

What is an action button in short answer? ›

An action button is a built-in shape you can add to your slides and set to hyperlink to another slide, play a sound, or perform some other action. This is a great way to add interactivity and navigation to your presentation with minimal effort.

Is forking the same as branching? ›

Fork is another way of saying clone or copy. The term fork (in programming) derives from a Unix system call that creates a copy of an existing process. So, unlike a branch, a fork is independent from the original repository. If the original repository is deleted, the fork remains.

Why you should rebase instead of merge? ›

But, instead of using a merge commit, rebasing re-writes the project history by creating brand new commits for each commit in the original branch. The major benefit of rebasing is that you get a much cleaner project history. First, it eliminates the unnecessary merge commits required by git merge .

Should I squash and merge in pull request? ›

As a general rule, when merging a pull request from a feature branch with a messy commit history, you should squash your commits. There are exceptions, but in most cases, squashing results in a cleaner Git history that's easier for the team to read.

What is difference between merge and cherry pick? ›

With the cherry-pick command, Git lets you incorporate selected individual commits from any branch into your current Git HEAD branch. When performing a git merge or git rebase , all the commits from a branch are combined.

Is git cherry pick good? ›

git cherry-pick is a useful tool allowing you to copy a commit from anywhere in your repository and append it to the HEAD of the current branch. This makes it an incredibly useful tool that can be utilised in a variety of ways, but it is often best practice to avoid overuse.

Does cherry pick copy or move? ›

Cherry picking can cause duplicate commits and many scenarios where cherry picking would work, traditional merges are preferred instead.

Are pull requests a bottleneck? ›

These pull requests can create bottlenecks because they are more likely to become stale, require rework, or lead to painful merge conflicts. We built a Lead Time Dashboard to help teams uncover which pull requests are causing delays and prioritizing reviews.

Why small pull requests are better? ›

Small pull requests get faster code reviews

The longer it takes to review the pull request, the more likely it is that it won't be done in one go. With large pull requests, reviewers often lose their focus and get pulled into other stuff.

Can I raise 2 pull requests from same branch? ›

How to stack pull requests. To stack two PRs, checkout the first branch from your base master (or develop ) and push your changes. Create the PR with the base as master . Then, checkout the second branch from the first.

What is the difference between global and object-specific quick actions? ›

In the Salesforce mobile app, object-specific actions show up on record detail pages. So for example, an action associated with the opportunity object is only available when a user is looking at an opportunity. Global actions let users create records, but the new record has no relationship with other records.

What are global quick actions? ›

You can add global quick actions to almost any page that supports actions. Use global actions to let users log call details, create or update records, or send email, all without leaving the page they're on.

What is quick action in Visual Studio? ›

Quick Actions let you easily refactor, generate, or otherwise modify code with a single action. Quick Actions are available for C#, C++, and Visual Basic code files. Some actions are specific to a language, and others apply to all languages.

What is quick action in epic? ›

In fewer clicks you can use QuickActions to perform routine follow up. Use Result Note QuickActions in In Basket to enter your standard result note text, route a Result Note message to your preferred recipients, and even mark the associated Results message as Done.

Can we call quick action in lightning component? ›

You can only use the Quick Action API on a lightning record page. You also have to include the quick action on the page layout (mobile & lightning experience actions section) for it to be available for use.

What is a capability of object-specific quick actions? ›

Object-specific actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.

What are the four priority areas for global action? ›

The GAP focuses on generating and scaling up action, around five priority action areas. These are to advance policy, transform learning and training environments, build the capacities of educators and trainers, empower and mobilize youth and accelerate sustainable solutions at a local level.

Why do we need global action? ›

Without global coordination and regulation, common resources risk degradation. Our climate is changing. Temperature is rising. Rainfall patterns are becoming erratic and unpredictable.

How do I create a global quick action? ›

Create Global Quick Actions
  1. From Setup, enter Actions in the Quick Find box, then select Global Actions.
  2. Click New Action.
  3. Select the type of action to create.
  4. Customize the action. ...
  5. Enter a label for the action. ...
  6. If necessary, change the name of the action. ...
  7. Type a description for the action.

How do I add a button to quick action? ›

Add Create New Visit Quick Action Button
  1. In Setup, go to the Object Manager and select Emergency Request.
  2. Under Buttons, Links, and Actions, click New Action. For Action Type, select Create Record. For Target Object, select Visit. For Label, provide the label the user sees, such as Request Supplies. ...
  3. Click Save.

How do you use the lightning component in quick action? ›

  1. In Setup, click Object Manager, click the object that you want to create the action for, and click Buttons, Links, and Actions.
  2. Click New Action.
  3. For Action Type, select Lightning Component.
  4. Select the component that you want the action to call.
  5. Enter a label for the action. ...
  6. If necessary, change the name of the action.

How do I edit quick actions? ›

To configure or change existing Quick Steps, do the following:
  1. In Mail, select Home.
  2. In the Quick Steps group, select the More. ...
  3. In the Quick Step box, select the Quick Step that you want to change, and then select Edit.
  4. Under Actions, change or add the actions that you want this Quick Step to do.

What is the Quick Actions menu? ›

The Quick Actions menu provides you with quick access to commonly used functions of the app. To open the Quick Actions menu, tap the access_time icon on the right side of the Command bar. The menu is split into two parts, the top icon row and the main body of the menu.


1. A Quick GitLab and GitIgnore Example
(Cameron McKenzie)
2. GitLab CI CD Tutorial for Beginners [Crash Course]
(TechWorld with Nana)
3. GitLab Onboarding Quick Guide
(GitLab Unfiltered)
4. GitLab CE Tutorial #6 - Merge Requests
5. Continuous Integration with GitLab (overview demo)
6. #8 GitLab Tutorial for Beginners | Git Tags | Easy Explanation
Top Articles
Latest Posts
Article information

Author: Carmelo Roob

Last Updated: 03/04/2023

Views: 5515

Rating: 4.4 / 5 (65 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Carmelo Roob

Birthday: 1995-01-09

Address: Apt. 915 481 Sipes Cliff, New Gonzalobury, CO 80176

Phone: +6773780339780

Job: Sales Executive

Hobby: Gaming, Jogging, Rugby, Video gaming, Handball, Ice skating, Web surfing

Introduction: My name is Carmelo Roob, I am a modern, handsome, delightful, comfortable, attractive, vast, good person who loves writing and wants to share my knowledge and understanding with you.