Skip to content

New Integration Request - Local File System #13597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ghanique opened this issue May 25, 2025 · 0 comments
Open

New Integration Request - Local File System #13597

ghanique opened this issue May 25, 2025 · 0 comments

Comments

@ghanique
Copy link

ghanique commented May 25, 2025

Describe your current workflow

  1. Integrate the workspace with GitHub
  2. Make changes to the source code implementation
  3. Make changes to the collection
  4. Commit the changes to the source code
  5. Commit the changes to the collection
  6. Pull changes from the remote git repo
  7. Use interactive rebase to merge the changes to my code to the changes made in postman because they belong together.

Describe your ideal workflow

  1. Pull master in the local repository
  2. Start Postman
  3. Postman automatically loads the collection from the local repository.
  4. Make changes to both the source code and to the Postman collection.
  5. Postman automatically saves changes to the collection to the collection file in the local repository.
  6. Changes to the collection file can be committed together with changes to the source code.

Describe alternatives you've considered

  1. Pull master in the local repository
  2. Start Postman
  3. Import the collection from the local repository
  4. Make changes to the source code and to the Postman collection.
  5. Export the collection to the local repository
  6. Commit the changes to the collection together with the changes to the source code.

The downside of this method is that it requires extreme discipline from the developer to ensure that he doesn't overwrite changes made by other developers, or that his changes are actually being committed together with the code changes.

Additional context

My main problem with Postman is that the life cycle of the source code is identical to the life cycle of the Postman Collection. However, because Postman implements its own life cycle, whatever is in Postman is (almost) always out of sync with what is in the repository. Additionally, using Postman without a GitHub integration makes it impossible to roll back both the source code as well as the Postman collection to the same point in time.

The GitHub integration addresses this to some extend, but it forces that Postman creates its own commits. So even though the commit of Postman and the commit of the Developer should have been one commit, there are now two commits, obfuscating the intent and making the general timeline in git hard to read and interpret.

There is a GitHub, GitLab, and BitBucket integration, but if you have your own Git server, you're ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants