Update links to /ci/lint with a new project's ci/lint
What does this MR do?
Replaces all remaining links to /ci/lint after !17729 (merged) with ones to the project's ci/lint.
Are there points in the code the reviewer needs to double check?
You can use git grep -n '\bci_lint_path'
for the coverage.
Why was this MR needed?
As /ci/lint after !17729 (merged) is meaningless and direct links to the project's ci/lint would be more helpful.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary - [n/a] Documentation created/updated
- [n/a] API support added
-
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend - [n/a] Has been reviewed by Backend
- [n/a] Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together - [n/a] Internationalization required/considered
- [n/a] End-to-end tests pass (
package-and-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #45666 (closed)
Edited by Takuya Noguchi