The id of collection variables change in the collections file and cause conflict in git

[dparadisZentelia]

Is there an existing issue for this?

• [X] I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

When we run a collection in Postman, the ids of variable changes and cause problem when we have to merge many change in git. We could see it when we try to display the change in the suggest commit, because is empty.

When peoples in my teams commit by accident, And and review the pull request, I have to reject, because no value is commit on the collection file. My suggestion, stop to change the id value of variable in the json collection file, because no value to commit it.

Steps To Reproduce

1. In Postman Open a workspace link to git
2. Select a branche
3. Run a collection when the collection change variable collection value (normally this change should be local)
4. Open the git panel and see the collection suggest for commit
5. Click on the see diff icon No change is display.

Screenshots or Videos

No response

Operating System

macOs

Postman Version

10.16.3

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[dparadisZentelia]

Any news about it? This behaviour don't help to merge collection. The goal of the Postman feature to be able store collection in repos is to simplify the life when we work together on the same collection!

[MichaelRemillard]

+1

[sony-mathew]

Hey @dparadisZentelia , we are looking into this issue. Will update here once we have a fix ready.

[dabelairpaulo]

+1

[MaximeSanschagrin]

Hey i work for the same company as OP reporter and we still have the issue. where we have merge conflicts that blocks the Pr due to Postman id on collection variable being changed but we have absolutely no control over this.