Add gl-form-input class for fields in fogbugz import page
What does this MR do?
Add gl-form-input class for fields in fogbugz import page
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#2524 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2585 (closed)
added devopsmanage frontend sectiondev + 1 deleted label
added Category:Importers UI polish UX typemaintenance labels
added typefeature label
mentioned in issue gitlab-org/quality/triage-reports#2633 (closed)
added 3090 commits
-
7292d662...9d9b902a - 3087 commits from branch
gitlab-org:master
- 3a8a053d - Add gl-form-input class for fields in fogbugz import page
- a8e7e037 - Add Changelog
- 4c535306 - Update gl-form-fogbugz-import.yml
Toggle commit list-
7292d662...9d9b902a - 3087 commits from branch
Can anyone please review this MR
🙇 mentioned in issue gitlab-org/quality/triage-reports#2817 (closed)
changed milestone to %13.12
mentioned in commit 290073d1
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#2981 (closed)
added releasedcandidate label
removed typefeature label
added groupimport and integrate label and removed 1 deleted label