Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
tails
tails
Commits
83100c51
Commit
83100c51
authored
Dec 07, 2015
by
bertagaz
Browse files
Restrict WIP branches name to the one prefixed by `wip/` only.
parent
4bf6ecce
Changes
1
Hide whitespace changes
Inline
Side-by-side
wiki/src/contribute/git.mdwn
View file @
83100c51
...
...
@@ -174,12 +174,11 @@ should be forked off the devel branch.
If you intend to work on a branch not really meant to be proposed to a
merge at first, like an experimenting branch that you still want to push
to share with other developers, you can add the keyword `wip` or `WIP`
after the topic prefix explained above (e.g `feature/wip-*`). It will
make it clear to everyone that this branch shouldn't be merged before
being renamed, and our Jenkins instance will not build and test it, so
you won't get notifications for a branch that you know is breaking the
build and/or the test suite.
to share with other developers, you can prefix its name by the keyword
`wip/`. It will make it clear to everyone that this branch shouldn't be
merged before being renamed, and our Jenkins instance will not build nor
test it, so you won't get notifications for a branch that you know is
breaking the build and/or the test suite.
#### experimental
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment