Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-pylib
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
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
Code review analytics
Issue 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
caosdb
Software
caosdb-pylib
Commits
3bf862b9
Unverified
Commit
3bf862b9
authored
4 years ago
by
Daniel
Browse files
Options
Downloads
Patches
Plain Diff
DOC: Gitlab merge template.
parent
807ac912
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/merge_request_templates/General.md
+29
-0
29 additions, 0 deletions
.gitlab/merge_request_templates/General.md
with
29 additions
and
0 deletions
.gitlab/merge_request_templates/General.md
0 → 100644
+
29
−
0
View file @
3bf862b9
Insert a meaningful description for this merge request here. What is the
new/changed behavior? Which bug was fixed?
---
Add the text above this line to the git comment.
# Check list for the author #
-
[ ] All tests pass. (style, unit/integration, static code analysis)
-
[ ] What is the main focus for the reviewer? What is the core intent of this
MR?
-
[ ] How to set up a test environment.
-
[ ] Annotations in code (Gitlab comments)
-
Intent of new code
-
Problems with old code
-
Why this implementation?
# Check list for the reviewer #
-
[ ] Tests pass
-
[ ] Do I understand the intent of this MR?
-
[ ] Does the test environment setup work?
-
[ ] Is the intended behavior reproducible in the test environment?
-
[ ] Code overview: Which functions/classes are relevant for understanding the MR?
-
[ ] Work through the open comment threads.
-
[ ] Are the doc strings / comments up-to-date? Or have there been behavioral
changes without amending the documentation?
-
[ ] Are there spezifications? Are they satisfied?
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