Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
JPSeditor
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
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
JuPedSim
JPSeditor
Wiki
Docs
Contributing
workflow
Changes
Page history
New page
Templates
Clone repository
Copied stuff from jpscore. just to test
authored
9 years ago
by
Erik Andresen
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/contributing/workflow.md
+47
-0
47 additions, 0 deletions
docs/contributing/workflow.md
with
47 additions
and
0 deletions
docs/contributing/workflow.md
0 → 100644
View page @
0ce2d976
# Workflow
This is a git-specific workflow that helps you contribute flawlessly you JuPedSim.
-
Clone the project (for the first time)
```
python
git
clone
https
:
//
cst
.
version
.
fz
-
juelich
.
de
/
jupedsim
/
jpscore
.
git
```
-
Change to the developement branch and create a branch with your feature.
```
python
git
checkout
developement
git
checkout
-
b
feature_name
```
-
Write code and Commit changes
```
python
git
commit
-
m
"
Describe here your changes
"
```
-
Push your branch to GitLab. But before doing so,
[
test
](
pushing
)
your code.
```
python
git
push
origin
feature_name
```
-
Create a merge request
a *Master* will review your code & merge it to the developement branch (maybe).
## Tips Working with Git
1.
Pull frequently.
2.
Commit often, but don’t push every commit.
3.
Create one commit per unit of work. Break your changes down into multiple commits, e.g. "fix bug", "add documentation", etc.
4.
Push when changes are tested.
See also
[
8 Tips to help you work better with Git
](
https://about.gitlab.com/2015/02/19/8-tips-to-help-you-work-better-with-git/
)
.
__
_
**Top Tip**
: Your code is maybe fine if you see on the repository's front page this symbol

before your commit.
This diff is collapsed.
Click to expand it.