Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
iMSTK
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Analyze
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
Ben Boeckel
iMSTK
Commits
507fbeeb
Commit
507fbeeb
authored
3 years ago
by
Harald Scheirich
Browse files
Options
Downloads
Patches
Plain Diff
ENH: add pr message
See merge request
iMSTK/iMSTK!584
parent
845dd6c5
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/merge_request_templates/feature.md
+33
-0
33 additions, 0 deletions
.gitlab/merge_request_templates/feature.md
with
33 additions
and
0 deletions
.gitlab/merge_request_templates/feature.md
0 → 100644
+
33
−
0
View file @
507fbeeb
<!-- The text within this markup is a comment, and is intended to provide
guidelines to open a Pull Request for the iMSTK repository. This text will not
be part of the Pull Request. -->
<!-- See the
[
Contributing guidelines
](
https://gitlab.kitware.com/iMSTK/iMSTK/-/blob/master/CONTRIBUTING.md
)
. Specifically:
Start commit messages with a standard prefix (and a space):
*
BUG: fix for runtime crash or incorrect result
*
COMP: compiler error or warning fix
*
DOC: documentation change
*
ENH: new functionality
*
PERF: performance improvement
*
STYLE: no logic impact (indentation, comments)
*
WIP: Work In Progress not ready for merge
*
REFAC: Refactoring the code
Provide a short, meaningful message that describes the change you made.
When the PR is based on a single commit, the commit message is usually left as
the PR message.
-->
## PR Checklist
-
[ ] No API changes were made (or the changes have been approved)
-
[ ] No major design changes were made (or the changes have been approved)
-
[ ] No new dependecies were added (or the new dependencies have been approved)
-
[ ] Added test (or behavior not changed)
-
[ ] Updated API documentation (or API not changed)
-
[ ] Ran the
`CodeFormatEnforcer`
task and verified the header is in all new files
-
[
] Added [iMSTK examples
](
https://gitlab.kitware.com/iMSTK/iMSTK/-/tree/master/Examples
)
for all new major features (if any)
<!-- **Thanks for contributing to iMSTK!** -->
\ No newline at end of file
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