Remove commit_pipelines webpack entry point
All threads resolved!
All threads resolved!
What does this MR do?
Remove commit_pipelines webpack entry point
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Edited by Clement Ho
Merge request reports
Activity
mentioned in issue #41341 (closed)
added 11 commits
-
4ebfa4b0...b5325655 - 10 commits from branch
master
- c737646d - Merge branch 'master' into refactor-pipelines-list
-
4ebfa4b0...b5325655 - 10 commits from branch
assigned to @iamphill
mentioned in commit a4885b8f
mentioned in merge request !15695 (merged)
mentioned in commit 57e7b270
Please register or sign in to reply