Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
duniter-rs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
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
Éloïs
duniter-rs
Commits
c9edfe7a
Commit
c9edfe7a
authored
7 years ago
by
nanocryk
Browse files
Options
Downloads
Patches
Plain Diff
[fix] remove ordered list and fix rendering issue
parent
381d1206
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
CONTRIBUTING.md
+11
-13
11 additions, 13 deletions
CONTRIBUTING.md
with
11 additions
and
13 deletions
CONTRIBUTING.md
+
11
−
13
View file @
c9edfe7a
...
...
@@ -82,15 +82,13 @@ Please note we have a specific workflow, please follow it in all your interactio
## Merge Process
1.
Ensure any install or build dependencies are removed before the end of the layer when doing a
-
Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
1.
Ensure you rebased your branch on the latest
`dev`
commit to avoid any merge conflicts.
1.
Update the README.md with details of changes to the interface, this includes new environment
-
Ensure you rebased your branch on the latest
`dev`
commit to avoid any merge conflicts.
-
Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
1.
Increase the version numbers in any examples files and the README.md to the new version that this
-
Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is
[
SemVer
](
http://semver.org/
)
:
If the create is in developement stage, its format is 0.X.Y. In production stage, it's X.Y.Z.
...
...
@@ -102,5 +100,5 @@ Please note we have a specific workflow, please follow it in all your interactio
Your crate should always start with 0.1.0 version and only pass in 1.0.0 when no big changes are
planned. There is no need to rush a 1.0.0, take your time :)
1.
You may merge the Merge Request in once you have the sign-off of two other developers. If you
-
You may merge the Merge Request in once you have the sign-off of two other developers. If you
do not have permission to do that, you may request the second reviewer to merge it for you.
\ No newline at end of file
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