Sharing through git
A project is shared through its own git repository. gurl writes the project as one readable JSON document, and your own git command line moves it, with your keys and your credential helper.
Setting it up
Open the project, go to Git sharing, and either clone a repository a colleague shared or point the project at a folder. A folder with no remote works too: push commits and stops, until you add a remote.
| Action | What it does |
|---|---|
| Pull and import | Pulls the repository and brings in what the team changed. |
| Export and push | Writes the project document, commits and pushes. |
| Push on save | Pushes after every save. |
What does not travel
Secrets stay on the machine that typed them. A colleague receives the header name, the auth scheme, the OAuth token URL and client id, and the name of the variable, then fills in the value themselves.
Held back are passwords, tokens and client secrets, every parameter you marked with the lock, every parameter whose name says it holds a credential, and the value of every secret variable. A reference such as {{token}} does travel, because it is a name and not a secret.
Conflicts
When a request changed both here and in the repository, the repository keeps the request and your version is kept beside it as a copy titled with the word conflict and a date. That copy stays local until you choose to share it. Nothing is merged silently.