Create gitlab cheat sheet
We probably should create a Gitlab cheat sheet somewhere containing tips and tricks around our Gitlab interactions which might be helpful for a lot of us. #29 (closed) has something related to email interactions but there is more.
Activity
One thing I think @gaba was looking for was to how to reply to a comment in the GUI with quoting previous comment text. The "Reply" button only creates a new comment without any quoted text by default.
It seems the solution to that is currently highlighting the text to quote and then pressing the
r-key.
my "cheat sheet" is this document right now:
https://help.torproject.org/tsa/howto/gitlab/
I hope to migrate this into a gitlab wiki (https://gitlab.torproject.org/tpo/tpa/services/-/issues/34437) but until then, that is hosted in a ikiwiki which anyone can contribute to. You can see the repository source here:
https://gitweb.torproject.org/project/help/wiki.git/
... and clone it with:
git clone https://git.torproject.org/project/help/wiki.git/... and if you have write access to git, you can also push directly with this instead:
git clone git@git-rw.torproject.org:project/help/wiki.git/That said, I am happy to keep building that documentation with input from folks and I'm trying to keep an eye out for stuff like this! :) So I'll add @gk's tip in there, and will keep this issue open for a little longer in case people have specific questions or things they want to add tot he "Tutorial" section.
(Or did folks mean an actual cheatsheet, like a one-page, super-tightly-formatted-graphic-design-thing-that-people-can-print-but-mostly-never-do? :))
Edited by anarcatmentioned in commit wiki-archive@8d7119b2
mentioned in issue team#33769 (closed)
added Next label
assigned to @gaba
Just wanted to note that this "cheat sheet" is probably something that already exists in gitlab own docs. We haven't changed much of the way gitlab UX works. More importantly if we duplicate documentation we might miss that gitlab might change its own UX moving forward and our cheat sheet might soon become obsolete.
unassigned @gaba