Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
EnPT
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
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
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
EnMAP
GFZ_Tools_EnMAP_BOX
EnPT
Wiki
development guidelines
Changes
Page history
New page
Templates
Clone repository
Update development guidelines
authored
8 years ago
by
Andre Hollstein
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
development-guidelines.md
+12
-1
12 additions, 1 deletion
development-guidelines.md
with
12 additions
and
1 deletion
development-guidelines.md
View page @
8c6fc3d8
...
...
@@ -3,13 +3,24 @@
## This is common understanding and should be followed
*
All code in MASTER should adhere to PEP8 (https://www.python.org/dev/peps/pep-0008/)
*
MASTER should always work and pass all tests
*
Write documentation.
*
Write documentation
(docsrtings and rst docs)
.
*
All code is Python 3.5+
*
Use git as version control system: https://git-scm.com/
*
For command lines we use argparse: https://docs.python.org/3/library/argparse.html
*
We use continuous integration: https://about.gitlab.com/features/gitlab-ci-cd/
*
????
## How to develop
### Bugfix / New Feature
1.
make new branch
*
develop
*
build feature
*
test
*
write docs
*
build docs
*
???
## Tips and Tricks
*
Python IDE for profies: https://www.jetbrains.com/pycharm/
*
For any development question there is: https://stackoverflow.com/
This diff is collapsed.
Click to expand it.