Commit 05f742e9 authored by intrigeri's avatar intrigeri
Browse files

Document where to push "code" branches for review (refs: #15186).

Let's not implicitly suggest one can push directly to our repository on Salsa:
it's meant to be a read-only mirror of our canonical repo, and any changes made
directly on Salsa will be overwritten next time someone pushes _anything_ to the
canonical tails.git.
parent 28eb34b7
......@@ -7,6 +7,11 @@ branch name, e.g. `bugfix/7173-upgrade-syslinux`.
When you think it is good enough and have tested it, you have to:
- Push your branch
- If you have commit access to the official Tails Git repository,
push your branch there so our CI picks it up.
- Else, push to your personal Git repository:
[fork us on Salsa](https://salsa.debian.org/tails-team/tails).
- Set the ticket's *Status* field to *In Progress* (if you do not see
this field when editing the ticket, ask the [[sysadmin team|contribute/working_together/roles/sysadmins]]
to grant you the necessary permissions).
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment