Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
duniter
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
nodes
typescript
duniter
Commits
b5e3a9c9
Commit
b5e3a9c9
authored
4 years ago
by
Éloïs
Browse files
Options
Downloads
Patches
Plain Diff
[doc] remove branch naming
parent
dc75e571
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/dev/git-conventions.md
+0
-32
0 additions, 32 deletions
doc/dev/git-conventions.md
with
0 additions
and
32 deletions
doc/dev/git-conventions.md
+
0
−
32
View file @
b5e3a9c9
...
@@ -14,38 +14,6 @@ The summary gives an overview of the rules described below. Reading it will help
...
@@ -14,38 +14,6 @@ The summary gives an overview of the rules described below. Reading it will help
-
clean commit history, understandable and concise
-
clean commit history, understandable and concise
-
contribution approved by a reviewer
-
contribution approved by a reviewer
## Branch naming
### Branch created by Gitlab
Most of the time, you'll use the "create a merge request" button and
Gitlab will name your branch. In that case, please prefix the name of
your branch with the branch type, for example:
fix/issue-test
### Branch created manually
On all cases anyway, your branch must start by your gitlab account's
username, so than everybody knows who's working on it. Also add it its
type, following this model:
type/description
type := see "Branch types" below.
description := short summary in present form, 3 to 4 words maximum, no articles.
Example:
ref/rename_trait_module
## Branch type
-
feature : add a feature
-
ref : refactoring existing code
-
fix : fix a bug in
`dev`
branch
-
hotfix : fix à bug in a stable release
## Naming commits
## Naming commits
Every commit must follow this convention:
Every commit must follow this convention:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
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!
Save comment
Cancel
Please
register
or
sign in
to comment