Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-cpplib
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
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
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
caosdb
Software
caosdb-cpplib
Merge requests
!42
Release 0.2.0
Code
Review changes
Check out branch
Open in Workspace
Download
Patches
Plain diff
Expand sidebar
Closed
Release 0.2.0
release-0.2.0
into
main
Overview
0
Commits
87
Pipelines
1
Changes
10
Closed
Timm Fitschen
requested to merge
release-0.2.0
into
main
2 years ago
Overview
0
Commits
87
Pipelines
1
Changes
10
0
0
Merge request reports
Viewing commit
40d7c9eb
Prev
Next
Show latest version
10 files
+
268
−
244
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
Files
10
Verified
40d7c9eb
Merge branch 'dev' into f-grpc-f-acm
· 40d7c9eb
Timm Fitschen
authored
3 years ago
.gitlab/merge_request_templates/Default.md deleted
100644 → 0
+
0
−
49
View file @ 76ce7133
# 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
-
[ ] 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 specifications? 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
Loading