Blog: Improve your GitLab productivity with these 10 tips (Feb 17)
Proposal
Often a hidden gem, similar to keyboard shortcuts, the quick actions enable you to stay within the browser and avoid navigating away from the issue/MR context: https://docs.gitlab.com/ee/user/project/quick_actions.html
With the new rebase action in 13.8, there are multiple additions for better workflows, e.g. /rebase
and live search auto-complete.
- https://twitter.com/dnsmichi/status/1353713703707938816
- https://twitter.com/dnsmichi/status/1353706451177525250
Next to quick actions, we can also incorporate features and workflows from the "GitLab uses GitLab" slide deck: https://docs.google.com/presentation/d/1bh-M-B1DUqstQfCDTnUr7T5YbBKOHfOH-8jfPCSJDDQ/edit
In 2019, I've discussed the quick action idea with @brendan on Twitter: https://twitter.com/dnsmichi/status/1199335562387156995
Community blog posts:
@rkuba: In general I can’t say how much I love quick actions, and having one for this is amazing. In the past these kind of operations were referred to as GitOPS which makes it sound even more awesome. I hope we do a have a cool video on the quick actions and stuff, as even our engineers are often not fully leveraging them. /label /assign /reviewer … all of those are incredibly powerful.
The idea is a collaborative blog post from @rkuba and me. @cbuchanan WDYT?
Blog draft
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title and apply the appropriate milestone (e.g. Blogs October 2020
) -
Give the issue a due date of a minimum of 2 working days prior -
If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
-
-
If time sensitive -
Add ~"Blog: Priority" label and supplied rationale in description -
Mention @rebecca
to give her a heads up ASAP
-
-
If wide-spread customer impacting or sensitive, mention @nwoods
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @arashidi
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @FionaOKeeffe
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if supporting an event or campaign -
Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)