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
234bd386
Verified
Commit
234bd386
authored
3 years ago
by
Daniel Hornung
Browse files
Options
Downloads
Patches
Plain Diff
MAINT: Moved issue templates to group.
parent
2f216cef
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#20042
failed
3 years ago
Stage: code_style
Stage: linting
Stage: setup
Stage: test
Stage: deploy
Changes
1
Pipelines
15
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/merge_request_templates/Default.md
+0
-50
0 additions, 50 deletions
.gitlab/merge_request_templates/Default.md
with
0 additions
and
50 deletions
.gitlab/merge_request_templates/Default.md
deleted
100644 → 0
+
0
−
50
View file @
2f216cef
# Summary
Insert a meaningful description for this merge request here. What is the
new/changed behavior? Which bug has been fixed? Are there related Issues?
# Focus
Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?
# Test Environment
How to set up a test environment for manual testing?
# Check List for the Author
Please, prepare your MR for a review. Be sure to write a summary and a
focus and create gitlab comments for the reviewer. They should guide the
reviewer through the changes, explain your changes and also point out open
questions. For further good practices have a look at
[
our review
guidelines
](
https://gitlab.com/caosdb/caosdb/-/blob/dev/REVIEW_GUIDELINES.md
)
-
[ ] All automated tests pass
-
[ ] Reference related Issues
-
[ ] Up-to-date CHANGELOG.md
-
[ ] Add type hints in created/changed code
-
[ ] Annotations in code (Gitlab comments)
-
Intent of new code
-
Problems with old code
-
Why this implementation?
# Check List for the Reviewer
-
[ ] I understand the intent of this MR
-
[ ] All automated tests pass
-
[ ] Up-to-date CHANGELOG.md
-
[ ] The test environment setup works and the intended behavior is
reproducible in the test environment
-
[ ] In-code documentation and comments are up-to-date.
-
[ ] Check: Are there spezifications? Are they satisfied?
For further good practices have a look at
[
our review guidelines
](
https://gitlab.com/caosdb/caosdb/-/blob/dev/REVIEW_GUIDELINES.md
)
.
/assign me
/target_branch dev
This diff is collapsed.
Click to expand it.
Daniel Hornung
@daniel
mentioned in issue
#100 (closed)
·
3 years ago
mentioned in issue
#100 (closed)
mentioned in issue #100
Toggle commit list
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