backstage: π Bug Report: Multiple Merge Request creation to same Gitlab Repo fail with 400 Bad request
π Description
Hi,
We are using the action: publish:gitlab:merge-request
in our Merge Request templates and generating the MR to an existing repo in Gitlab. First MR will be successful, however any subsequent MR with same branch name or different branch name fails with 400 Bad request
error.
Please let me know how can this be resolved?
π Expected behavior
The template should generate subsequent MRs successfully as long as the branch name is new.
π Actual Behavior with Screenshots
The publish action fails with below error.
Commit to branch failed
π Reproduction steps
- Create a software template with publish step using -
action: publish:gitlab:merge-request
- Try to publish the MR to an existing Gitlab repo. Once successful, merge the MR and close it.
- Try to create another MR to the same repo, it fails with above error.
π Provide the context for the Bug.
No response
π₯οΈ Your Environment
No response
π Have you spent some time to check if this bug has been raised before?
- I checked and didnβt find similar issue
π’ Have you read the Code of Conduct?
- I have read the Code of Conduct
Are you willing to submit PR?
None
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 38 (28 by maintainers)
GitLab API supports different
action
s per file, so the scaffolder action could be modified to make it per file/path, for example:instead of current approach where we use the same
commitAction
for all files@sharadpattanshetti Is there any update about this? Thanks!
Is there any news?
the issue is up for grabs @ichasco-heytrade!
@Rugvip and everyone sorry for the late reply. Had to check the policies before posting. Hope this helpsβ¦
sure @tudi2d . Occupied a bit with urgent deliverables now, will try in few days definitely. Before that I wanted your and @Rugvip opinion if this is the best way to achieve that functionality?
Thanks @sharadpattanshetti - sounds great. Would you be up for contributing a fix to this bug? π