Teams

Codestamp has no server and no account for teamwork. A team shares a collection through a Git repository it already has, and signing in stays with Git’s credential manager. Codestamp does not store the password or token.

Share and join

One collection is one repository. It can be on GitHub, GitLab, Bitbucket or Azure DevOps, or be a bare repository in a shared folder. The Collaboration button in the collection header opens the panel.

• Share: paste the repository address, enter a name and email (Codestamp suggests them from git config), and for an https address you can add a Git account username. Codestamp writes the collection and pushes it.
• Join: on the Import page, choose Join a shared collection and paste the same address. The collection arrives with the same ID as in the repository.
• To invite someone, add them to the repository on your Git host. Read-only access can receive changes but cannot send any.

An address must be https://, SSH or a folder path. Codestamp rejects ext::, file://, http://, and any address that holds credentials. Git must be installed (Git for Windows on Windows).

If you share into a repository that already has files, Codestamp looks first and shows a warning with the main branch and the files it would delete. Replace files and share puts the collection in their place in one ordinary commit on the main branch, with no force push, so the old files stay in history. It works only with the commit you reviewed. If someone pushes after your check, Codestamp stops and asks you to look again.

What the repository holds

Each request is its own file, in readable JSON with LF line endings, so diffs and reviews on your Git host stay clear.

Three things stay on your device: secret values (only the names are shared, and each member fills in their own), cookies and History, and the file paths picked for uploads and .proto files.

Sync now

Codestamp does not sync in the background. Your saved changes wait on your computer, and the header shows “not synced” until you press Sync now.

One sync commits your local changes with a message that says what changed, fetches, merges your team’s changes, and pushes. If the push is rejected because someone pushed first, Codestamp merges and tries again. Offline, the local commit waits for the next sync. Stop syncing unlinks the collection on this device only.

The header and the panel show the state: synced, not synced, offline, read-only, sign in, or a number of conflicts to resolve.

If Git cannot sign in, the panel shows a Sign in button. If the local copy of the repository is missing or damaged, Sync now clones it again from the last commit that synced, so your saved changes still go out as ordinary changes.

Merge and conflicts

Codestamp merges field by field with a 3-way merge, using the base version from Git.

• Edits to different fields of one request merge by themselves. One person changes the URL and another adds a header, for instance.
• Variable rows and sections merge by key. Request order merges without losing a new request. An edit wins over a delete.
• Only when two people change the same field does sync stop and show a conflict dialog. Each field shows your value and your teammate’s. You choose Keep mine, Take my teammate’s, or Keep both, in which case your version becomes a copy named “… (my copy)”.

Version history

In a team collection, the clock icon on a card lists the request’s versions from Git commits, with message, author and time. You can compare any version field by field with the current one and press Restore this version. A restore does not rewrite history. The old content is shared as a new change.

Tools › Git changes lists commits grouped by day, with the requests each one added, updated or removed, and a Requests tab that shows who last changed each request.

Git accounts

Each shared collection has its own account, so one collection can use a work account and another a personal one on the same host. For https addresses, the optional Git account username goes to Git’s credential manager. Settings › Git accounts lists the accounts, shows Signed in or Sign-in needed, and has Sign in, Sign out and Check. For SSH addresses, the SSH key decides the account. For two accounts on one host, use a host alias in ~/.ssh/config.

Access groups

Some values only part of the team should read. In Collaboration › Access groups, create a group such as “Prod”, then set a variable’s type to Restricted: Prod. Codestamp encrypts the value, and only devices of group members can read it. Anyone else with access to the repository sees the variable’s name, and the repository holds only the ciphertext.

1. Create the group. You become its first member.
2. Set a variable to Restricted for that group, then press Sync now.
3. A teammate presses Request access.
4. A member compares the device fingerprint (XXXX-XXXX-XXXX-XXXX, shown under This device) with the teammate over chat or a call, then presses Grant.

A device without access sees the row locked and cannot change or delete it. Remove gives the group a new key and re-encrypts its values. Because the removed person has already seen the old values, Codestamp lists the variables you should replace at their source.

Members can still copy values they can see. URLs, headers, bodies and scripts stay visible to anyone who can push, so review a teammate’s changes in Git changes. A token typed straight into Auth or a header is not protected, so move it into a variable. The CLI cannot open restricted values yet.