Most people know GitLab is a solid tool in today's DevOps workflows, with code reviews, CI/CD, and project management all available for users in a single application. But there are always ways to be more efficient. Since we use GitLab to develop GitLab, everyone has their own habits and hidden gems to speed things up.
We chatted about GitLab efficiency tips after seeing new quick actions releases in GitLab 13.8, and decided to share some of our favorite tips with GitLab users. We share our typical day-to-day workflows as an engineering manager (Roman) and a developer (Michael) to show how quick actions make teams more productive and efficient.
Roman: Engineering manager starts planning
I am an engineering manager on the Create: Editor team at GitLab. One of my responsibilities is capacity planning with product managers. Planning happens every month for the next GitLab release. GitLab uses the milestone feature to keep everything organized for the release. As planning goes on, I need to create a new issue for a new feature in the Web IDE. The issue description uses a description template which gets filled with the right context.
But instead of searching for the assignee in the dropdown, I just add a new line:
All quick actions start with a
/ character and will be interpreted by GitLab when the issue gets created. In addition to an assignee, issue labels need to be applied as well.
You can also assign multiple labels at once:
/label ~devops::create ~group::editor ~"Category::Web IDE"
How to apply multiple labels using GitLab quick actions.
The issue needs to be assigned to the next milestone. This can be done with another quick action:
Note that 13.9 release planning already happened last month. The product kickoff highlights the planned features.
The keyboard shortcut
cmd + enter now creates the issue without clicking a button.
So far, we were able to complete a lot of the necessary workflows around issues in one go, and without ever leaving the text box.
After reviewing the issue I created, I remembered that this issue should be assigned to the
FY22Q1 Performance OKRs epic. Again, we can use a quick action. It’s important to note here that referencing an epic works with the
& character. When we type this character, we can start to search for the epic by typing its name.
/epic & <search>
This will turn into something like this:
All quick actions can be used in a new comment and again using
cmd + enter to save it.
FY22Q1 Performance OKRs epic still needs to be added to a parent engineering OKR epic. So I'll navigate to the now-linked epic and use another quick action to set the parent epic.
/parent_epic & <search>
When working with multiple levels of epics, remember to keep practicing quick actions to create visual epic trees quickly. That’s all for now from my manager's side.
Michael: A developer starts with code
I work on the Developer Evangelism team at GitLab, and although I'm not technically a developer in the typical sense I still work with code on a daily basis. The average day starts with a new to-do. Today's to-do points me to the new issue that Roman created. After reviewing the issue requirements and defining the changes to be implemented, I start work: I'll clean up the work environment, pull the latest changes from the default branch (main/master), and create a new Git branch in my local terminal.
After a few commits, my work day nears its end. I decide to publish the local Git branch and create a new Merge Request (MR). After creating the MR, the triage workflow kicks off. I mark the MR as draft to prevent the workflow from starting before the MR is ready:
The next day, I continue working on the MR and finish everything that was planned, so I need to remove the draft designation. The
draft quick action is a toggle, so I can use it to assign and remove the
The next step is to assign a reviewer for the MR. GitLab 13.7 added merge request reviewers, which means we can leave the MR assignee untouched. I'll use the livesearch to assign the right reviewer with a leading
/assign_reviewer @ <search>
How to remove the draft and add a reviewer using GitLab quick actions.
After the first round of review, I get feedback and items for follow-up. Since I am in the middle of a different tasks, I create a new to-do to remind myself of an open task to follow up on when I'm ready.
Since my work as a developer evanglist includes many topics and areas, I get distracted with other high priority tasks throughout the day. Later in the week, I'll come back to the MR. The review items have been addressed by team member suggestions and all threads are resolved now. The reviewer approves the MR with the quick action:
The review process took a little while to complete, and because GitLab is a fast-changing project, the Git branch is outdated. I need to rebase against the default branch.
But since I am already working on something else, I do not want to stop what I am doing currently to rebase. Then I remember: GitLab 13.8 added the
/rebase quick action. This schedules a new background job that attempts to rebase the branch, and stops operations if it fails.
I open the MR and create a new comment. I start typing the rebase quick action, followed by
cmd+enter to send it:
How to rebase with GitLab quick actions.
Phew. It worked. The CI/CD pipeline is running, and I believe that the rebase did not break anything. I go to click the "Merge after pipeline succeeds" button, and remember there's a quick action for that.
The quick action takes into account what is configured for the project: Either merge when the pipeline succeeds or add it to the Merge Train.
Everything happens automatically and I can continue working on other tasks. The manager (in this case, Roman) sees the issue being closed automatically using the
Closes keyword. That's all from my developer's side.
Tip: Automatically closing issues after the MR has been merged is an amazing workflow for everyone, assuming the manager has set the milestone accordingly.
At GitLab, we have documented our engineering workflows which can be followed more efficiently with the quick actions shown in this blog post.
Quick actions + description templates = ❤️
We demonstrated different ways quick actions can be used to complete common tasks more efficiently. But they do not always have to be applied manually. One shortcut is to just add them to description templates so you do not have to worry about remembering them all. This way, you can also automatically assign users, add labels, and much more based on the template you apply. Using description templates helps with project contributions and allows everyone to focus on the feature proposal or bug report.
Let’s try it! Create a new project, navigate into "Issues > Labels" and generate a default set of labels. Next, open the Web IDE and add a new file in
.gitlab/issue_templates/bug.md. Add the following content:
# Summary # Steps to reproduce 1. 1. 1. <!-- Do not edit the section below --> /label ~bug /assign @YOURUSER
First, replace YOURUSER with your username (make sure you're logged in). Commit the new file to the default branch, and navigate into the issue list. Next, create a new issue and select
bug from the dropdown. Add some content, and submit the issue. Finally, verify that the label and assignee are both set.
Tip: This is not limited to issue templates, it also works with MRs and epics. At GitLab we also often use this function to dynamically assign people based on reports created automatically. There are many opportunities to use description templates.
More tips and insights
We have not yet tried the following quick actions - can you help us out? :-)
Let us know in the comments below which quick actions most helped your productivity and if you have other creative ways of using quick actions.
PS: We also support shortcuts at GitLab, and the most loved shortcut is
cmd + k for inserting a Markdown URL.