Add gl-form-input for project issue template settings
What does this MR do?
Add gl-form-input for project issue template settings
As a part of https://gitlab.com/gitlab-com/marketing/community-relations/contributor-program/hackathon/-/issues/50
Screenshots (strongly suggested)
Before | After |
---|---|
![]() |
![]() |
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Merge request reports
Activity
👋 @yoThank you for your contributions to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!
Our Merge Request coaches will ensure your contribution is reviewed in a timely manner.
To bring your merge request to the attention of the relevant team within GitLab, you can ask our bot to label it with a group label. For example, if your merge request changes a project management feature, it can be labelled by commenting
@gitlab-bot label ~"group::project management"
. To find the most relevant group for your change, you can look up the group based on the most relevant product category in the product categories table. Once you have found the group name, type@gitlab-bot label ~group::
, then start to type the group name and select the applicable group label, then submit the comment and the bot will apply the label for you.If after a few days, there's no message from a GitLab team member, feel free to ping
@gitlab-org/coaches
or ask for help by commenting@gitlab-bot help
.These resources may help you to move your Merge Request to the next steps:
This message was generated automatically. You're welcome to improve it.
added Community contribution label
added Hackathon label
This MR will be considered part of the quarterly GitLab Hackathon for a chance to win a prize. Thank you for your contribution!
mentioned in issue gitlab-org/quality/triage-reports#2521 (closed)
added sectiondev label
mentioned in issue gitlab-org/quality/triage-reports#2620 (closed)
- Resolved by Miguel Rincon
Can anyone please review this MR
🙇
added 3435 commits
-
cb666be2...9d9b902a - 3433 commits from branch
gitlab-org:master
- 59458a52 - Add gl-form-input for project issue template settings
- c94da2e9 - Add Changelog
-
cb666be2...9d9b902a - 3433 commits from branch
changed milestone to %13.12
assigned to @yo
- Resolved by Yoginth
3 Warnings ⚠ 83dce8d4: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. ⚠ ac69ae98: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. ⚠ You've made some app changes, but didn't add any tests.
That's OK as long as you're refactoring existing code,
but please consider adding any of the tooling, ~"tooling::pipelines", ~"tooling::workflow", documentation, QA labels.1 Message 📖 We are in the process of rolling out a new workflow for adding changelog entries. This new workflow uses Git commit subjects and Git trailers to generate changelogs. This new approach will soon replace the current YAML based approach. To ease the transition process, we recommend you start using both the old and new approach in parallel. This is not required at this time, but will make it easier to transition to the new approach in the future. To do so, pick the commit that should go in the changelog and add a
Changelog
trailer to it. For example:This is my commit's subject line This is the optional commit body. Changelog: added
The value of the
Changelog
trailer should be one of the following: added, fixed, changed, deprecated, removed, security, performance, other.For more information, take a look at the following resources:
- gitlab-com/gl-infra/delivery#1564 (closed)
- https://docs.gitlab.com/ee/api/repositories.html#generate-changelog-data
If you'd like to see the new approach in action, take a look at the commits in the Omnibus repository.
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
Category Reviewer Maintainer frontend Zack Cuddy ( @zcuddy
) (UTC-5)Miguel Rincon ( @mrincon
) (UTC+2)If needed, you can retry the
danger-review
job that generated this comment.Generated by
🚫 DangerEdited by 🤖 GitLab Bot 🤖@zcuddy Would you mind reviewing this community contribution please?
requested review from @zcuddy
requested review from @mrincon
added 243 commits
-
79bc7cb5...43d23b09 - 239 commits from branch
gitlab-org:master
- ed6ba5d4 - Add gl-form-input for project issue template settings
- ac69ae98 - Add Changelog
- 51fd73f6 - Apply 1 suggestion(s) to 1 file(s)
- 83dce8d4 - Update gl-form-issue-template.yml
Toggle commit list-
79bc7cb5...43d23b09 - 239 commits from branch
enabled an automatic merge when the pipeline for 4e6c18df succeeds
enabled an automatic merge when the pipeline for 4e6c18df succeeds
mentioned in commit 088b5670
added workflowstaging label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
mentioned in issue gitlab-org/quality/triage-reports#2894 (closed)
added releasedcandidate label
added 1 deleted label and removed devopscreate label
added devopsmanage label and removed 1 deleted label