add link to concurrent devops
Add a link to the Concurrent DevOps page to show the benefits of using the ConDev Index (aka DevOps Index)
Merge request reports
Activity
Hi @williamchia,
Please add labels to your merge request, this helps triage community merge requests.
Thanks for your help!
Improve this comment
added auto updated label
@mikelewis can you please review/merge?
4 Errors c93582a1: The commit subject must start with a capital letter 1e5163f1: The commit subject must contain at least three words 1e5163f1: The commit subject must start with a capital letter 1e03f8a6: The commit subject must start with a capital letter 3 Warnings This merge request does not refer to an existing milestone. CHANGELOG missing. You can create one with:
bin/changelog -m 22071 "add link to concurrent devops"
If your merge request doesn’t warrant a CHANGELOG entry,
consider adding any of the ~backstage, ~Documentation, QA, test labels.
See the documentation.This merge request is missing the ~Documentation label. 1 Message This merge request adds or changes files that require a review from the docs team. Docs Review
The following files require a review from the Documentation team:
doc/user/instance_statistics/convdev.md
To make sure these changes are reviewed, mention
@gl-docsteam
in a separate comment, and explain what needs to be reviewed by the team. Please don't mention the team until your changes are ready for review.Commit message standards
One or more commit messages do not meet our Git commit message standards. For more information on how to write a good commit message, take a look at How to Write a Git Commit Message.
Here is an example of a good commit message:
Reject ruby interpolation in externalized strings When using ruby interpolation in externalized strings, they can't be detected. Which means they will never be presented to be translated. To mix variables into translations we need to use `sprintf` instead. Instead of: _("Hello #{subject}") Use: _("Hello %{subject}") % { subject: 'world' }
This is an example of a bad commit message:
updated README.md
This commit message is bad because although it tells us that README.md is updated, it doesn't tell us why or how it was updated.
Generated by
DangerEdited by 🤖 GitLab Bot 🤖@williamchia Just a reminder that when only making changes to /doc, using the special docs branch names will skip the unnecessary pipeline steps required for other code. But it doesn't really matter here since it was a small one-off without many commits, etc.
- Resolved by Mike Lewis
assigned to @williamchia
assigned to @mikelewis
enabled an automatic merge when the pipeline for c93582a1 succeeds
mentioned in commit 6faaa317
mentioned in issue gitlab-org/release/tasks#515 (closed)