Skip to main content
Question

Merge Conflict Resolved but Push to Mainframe Fails

  • June 15, 2026
  • 2 replies
  • 28 views

Hatixhe Kercuku

 I have encountered an issue while working with a component in my cloned package in VS Code. I recently made some changes to this component, and my colleague made other changes to the same component. As a result, I ran into a merge conflict when attempting to push my updates.

After carefully resolving the merge conflict and committing the changes, I tried to push back to the mainframe. However, I received an error, and I am not sure where the problem lies. I have double checked to ensure there are no non-mainframe compatible characters in both the merged source and my commit message.

Could someone please advise if there is something I am missing in the process, or if there could potentially be a bug in the git connector? Any guidance or troubleshooting tips would be greatly appreciated as I would like to get this resolved as soon as possible.

 

2 replies

Johan Jacob
Forum|alt.badge.img+1
  • Participating Frequently
  • June 19, 2026

@RocketSofware

Would anyone be able to let us know if there is an issue in the Git Connector with the merge process

  1. Developer one did a git clone and starts updating components locally
  2. Developer two stays on the mainframe and updates directly in the package
  3. Developer one performs a push to the package and gets a merge to be performed
    When the merge locally is done, the push crashes ​@Hatixhe Kercuku can you put the messages in this post please

Thank you
Johan


Hatixhe Kercuku

After the merge is performed, push fails. Even if you run “Pull” first, it gives the same error. 

 


​​​​​