Fix the following style-lint errors and warnings for `app/assets/stylesheets/pages/issues.scss`
Problem
Fix the following style-lint errors and warnings for app/assets/stylesheets/pages/issues.scss
15:7 ⚠ Expected ".issues-list .issue .issuable-meta .author-link" to have no more than 3 compound selectors selector-max-compound-selectors
15:7 ⚠ ".author-link" and ".issue-labels (app/assets/stylesheets/pages/issues.scss -10:5)" have the same properties. stylelint-gitlab/duplicate-selectors
19:7 ⚠ Expected ".issues-list .issue .issuable-meta .issuable-comments" to have no more than 3 compound selectors selector-max-compound-selectors
46:1 ⚠ Selector should be written in lowercase with hyphens selector-class-pattern
56:1 ⚠ "form.edit-issue" and "form (app/assets/stylesheets/pages/issues.scss -51:3)" have the same properties. stylelint-gitlab/duplicate-selectors
72:3 ⚠ Selector should be written in lowercase with hyphens selector-class-pattern
86:1 ⚠ ".merge-request-id" and ".author-link (app/assets/stylesheets/pages/issues.scss -15:7)" have the same properties. stylelint-gitlab/duplicate-selectors
116:3 ⚠ "&.merged" and "&.closed (app/assets/stylesheets/pages/issues.scss -111:3)" have the same properties. stylelint-gitlab/duplicate-selectors
190:1 ⚠ ".new-branch-col" and ".issues-nav-controls (app/assets/stylesheets/pages/issues.scss -153:1)" have the same properties. stylelint-gitlab/duplicate-selectors
261:1 ⚠ ".discussion-reply-holder .note-edit-form" and "svg (app/assets/stylesheets/pages/issues.scss -129:3)" have the same stylelint-gitlab/duplicate-selectors
properties.
285:7 ⚠ Expected ".emoji-block .row .create-mr-dropdown-wrap .btn-group:not(.hidden)" to have no more than 3 compound selectors selector-max-compound-selectors
What to do
- If possible, replace the CSS class with a utility one, check common.scss and https://getbootstrap.com/docs/4.3/utilities/ for existing ones
- Double check if all the warning have been fixed by running
yarn run stylelint-file app/assets/stylesheets/pages/issues.scss
- In the MR, add screenshots of the affected areas before and after the changes, check the first MR as a guideline
- If there are a lot of changes, we recommend to break them into smaller MRs
- Double check the usage of each changed class both in CE and EE
- EE changes should either be backported into CE or moved into
ee/
folder. You can read more about how to handle EE code here - Label the MR with gitlab-ce~10109752