diff options
| author | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2018-07-22 18:46:05 +0900 |
|---|---|---|
| committer | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2018-07-22 18:46:05 +0900 |
| commit | c7124c3d49c3c7616b093b28bcd97404390644a8 (patch) | |
| tree | e88d5c7586fed31aee66e92fc5838f57b7c1fda9 | |
| parent | 80effb5c44932ac0a409000623b31307e0c9784c (diff) | |
| download | buildstream-c7124c3d49c3c7616b093b28bcd97404390644a8.tar.gz | |
HACKING.rst: Added convention for naming of branches in merge requests.
| -rw-r--r-- | HACKING.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/HACKING.rst b/HACKING.rst index b5746d991..d92a20dd7 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -27,6 +27,9 @@ Branches must be submitted as merge requests in gitlab. If the branch fixes an issue or is related to any issues, these issues must be mentioned in the merge request or preferably the commit messages themselves. +Branch names for merge requests should be prefixed with the submitter's +name or nickname, e.g. ``username/implement-flying-ponies``. + You may open merge requests for the branches you create before you are ready to have them reviewed upstream, as long as your merge request is not yet ready for review then it must be prefixed with the ``WIP:`` |