Skip to content
Snippets Groups Projects

Add gl-form-input for project issue template settings

Merged Yoginth requested to merge yo/gitlabold:gl-form-issue-template into master
All threads resolved!

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
image image

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

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
Edited by Miguel Rincon

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • 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:

    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 🚫 Danger

    Edited by 🤖 GitLab Bot 🤖
  • @zcuddy Would you mind reviewing this community contribution please?

  • Reuben Pereira requested review from @zcuddy

    requested review from @zcuddy

  • Zack Cuddy requested review from @mrincon

    requested review from @mrincon

  • Zack Cuddy approved this merge request

    approved this merge request

  • Yoginth added 1 commit

    added 1 commit

    • 1b962e1f - Apply 1 suggestion(s) to 1 file(s)

    Compare with previous version

  • Yoginth added 1 commit

    added 1 commit

    • 79bc7cb5 - Update gl-form-issue-template.yml

    Compare with previous version

  • Yoginth added 243 commits

    added 243 commits

    Compare with previous version

  • Miguel Rincon marked the checklist item I have included a changelog entry. as completed

    marked the checklist item I have included a changelog entry. as completed

  • Miguel Rincon approved this merge request

    approved this merge request

  • Miguel Rincon resolved all threads

    resolved all threads

  • Miguel Rincon enabled an automatic merge when the pipeline for 4e6c18df succeeds

    enabled an automatic merge when the pipeline for 4e6c18df succeeds

  • Miguel Rincon canceled the automatic merge

    canceled the automatic merge

  • Miguel Rincon enabled an automatic merge when the pipeline for 4e6c18df succeeds

    enabled an automatic merge when the pipeline for 4e6c18df succeeds

  • merged

  • Miguel Rincon mentioned in commit 088b5670

    mentioned in commit 088b5670

  • added workflowcanary label and removed workflowstaging label

  • added workflowproduction label and removed workflowcanary label

  • 🤖 GitLab Bot 🤖 added 1 deleted label and removed devopscreate label

    added 1 deleted label and removed devopscreate label

  • 🤖 GitLab Bot 🤖 added devopsmanage label and removed 1 deleted label

    added devopsmanage label and removed 1 deleted label

  • Please register or sign in to reply
    Loading