This is example of my Jira Deployments section, all those commits are non merge commits
Hi @Alkaid Llanes ,
that information appears if the merge is managed through a pull request within bitbucket but not for gitlab. In my mind, this is correct because, merge commit should appear on the target branch and not on the source one.
Using Bitbucket, that operation appears because is related to pull request.
Fabio
Hi @Fabio Racobaldo _Herzum_ I probably don't explain myself so good, non english speaker here :(, the thing is that Jira is doing nothing with merge commits, but in the merge commit is where the deployments runs on gitlab, so the only way I have to see those deployments on jira, is doing it in normal commits, before the merge.. do I explain better?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.