You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When multiple people work on different features and customize the collection, merge conflicts arise.
Person A adds a request.
Person B changes the header of an existing request.
Both export the collection and create a pull request. The first pull request can be merged without any problems. With the second pull request, there are merge conflicts because the IDs and the modified timestamp have changed for each request.
I would like the IDs of requests and folders not to change with every export and to be created once the request/folder is created.
For the timestamps, an option, as in the question about the export of private environments, with which timestamps can be deactivated would be advantageous.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When multiple people work on different features and customize the collection, merge conflicts arise.
Person A adds a request.
Person B changes the header of an existing request.
Both export the collection and create a pull request. The first pull request can be merged without any problems. With the second pull request, there are merge conflicts because the IDs and the
modified
timestamp have changed for each request.I would like the IDs of requests and folders not to change with every export and to be created once the request/folder is created.
For the timestamps, an option, as in the question about the export of private environments, with which timestamps can be deactivated would be advantageous.
Beta Was this translation helpful? Give feedback.
All reactions