Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gdat
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
Model registry
Operate
Environments
Monitor
Incidents
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
SPC
gdat
Commits
b9760389
Commit
b9760389
authored
5 years ago
by
Olivier Sauter
Browse files
Options
Downloads
Patches
Plain Diff
rename head README to README_developer
contains guidelines for git and contributors
parent
39151ae5
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!9
rename head README to README_developer
Pipeline
#15392
passed
5 years ago
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README_developer
+3
-3
3 additions, 3 deletions
README_developer
with
3 additions
and
3 deletions
README
→
README
_developer
+
3
−
3
View file @
b9760389
...
...
@@ -9,9 +9,9 @@ git-hosted version currently under development for automated tests etc.
* To propose changes:
* Open an issue to discuss the matter (in gitlab project page -> issues)
* Then open a branch to work on the issue. There are several ways to do this:
* Click on 'create branch' on the issue page on gitlab (then `git fetch` and `git checkout <branchname>`)
* Click on 'create branch' on the issue page on gitlab (then `git fetch` and `git checkout <branchname>`)
* In your local space, do `git checkout -b <branchname>` to create a new branch from your current `HEAD`.
* When done, `git push` the branch and submit a merge request.
* When done, `git push` the branch and submit a merge request.
* The link to open the merge request is shown following the commit.
* Assign someone (other than yourself) to review the merge request.
* Follow up on any questions/comments and optionally amend your branch (and re-push) to fix any new issues that arise.
\ No newline at end of file
* Follow up on any questions/comments and optionally amend your branch (and re-push) to fix any new issues that arise.
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