sheppy/opendesk
1
0
Fork 0
mirror of https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk.git synced 2025-12-06 07:21:36 +01:00
Code Issues Packages Projects Releases Wiki Activity

chore(mr-templates): Improve wording in "Developer Checklist" section(s)

Browse Source
This commit is contained in:
Thorsten Roßner
2025-08-27 17:04:00 +02:00
parent a7400f0402
commit 5c771baa88
4 changed files with 38 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.gitlab/merge_request_templates/Bugfix.md
View File

@@ -44,14 +44,16 @@ Set labels:
/label ~"Testautomation::👀"
```
# 👷 Developer Checklist
# 👷 Developer Checklist
- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
- [ ] No.
- [ ] Yes, and the documentation was updated accordingly.
**Documentation:**
Document in an extra comment and link to that comment:
- [ ] How you verified the fix is working as expected, also in upgrade scenarios.
- [ ] Any regression testing done.
Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
- [ ] No
- [ ] Yes, and the documentation has been updated accordingly
--> Link to comment:
**Quality Assurance:**
- [ ] Verified that the feature works as expected, including upgrade scenarios
- [ ] Performed regression testing
- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
- ...

16
.gitlab/merge_request_templates/Feature.md
View File

@@ -36,12 +36,14 @@ Set labels:
# 👷 Developer Checklist
- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
- [ ] No.
- [ ] Yes, and the documentation was updated accordingly.
**Documentation:**
Document in an extra comment and link to that comment:
- [ ] How you verified the feature is working as expected, also in upgrade scenarios.
- [ ] Any regression testing done.
Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
- [ ] No
- [ ] Yes, and the documentation has been updated accordingly
--> Link to comment:
**Quality Assurance:**
- [ ] Verified that the feature works as expected, including upgrade scenarios
- [ ] Performed regression testing
- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
- ...

16
.gitlab/merge_request_templates/Other.md
View File

@@ -30,12 +30,14 @@ Set labels:
# 👷 Developer Checklist
- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
- [ ] No.
- [ ] Yes, and the documentation was updated accordingly.
**Documentation:**
Document in an extra comment and link to that comment:
- [ ] How you verified the change is working as expected, also in upgrade scenarios.
- [ ] Any regression testing done.
Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
- [ ] No
- [ ] Yes, and the documentation has been updated accordingly
--> Link to comment:
**Quality Assurance:**
- [ ] Verified that the feature works as expected, including upgrade scenarios
- [ ] Performed regression testing
- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
- ...

18
.gitlab/merge_request_templates/Update.md
View File

@@ -28,14 +28,16 @@ Set labels:
/label ~"Testautomation::👀"
```
## 👷 Developer Checklist
# 👷 Developer Checklist
- Does the MR include new bits and pieces (e.g. new secrets) that require documentation?
- [ ] No.
- [ ] Yes, and the documentation was updated accordingly.
**Documentation:**
Document in an extra comment and link to that comment:
- [ ] How you verified the update is working as expected, also in upgrade scenarios.
- [ ] Any regression testing done.
Does this MR introduce changes (e.g., new secrets, configuration options) that require documentation?
- [ ] No
- [ ] Yes, and the documentation has been updated accordingly
--> Link to comment:
**Quality Assurance:**
- [ ] Verified that the feature works as expected, including upgrade scenarios
- [ ] Performed regression testing
- Link to internal comment(s) with detailed QA results (to avoid exposing infrastructure details):
- ...