Team Collaboration
Dynomate stores request collections as files in directories that you choose. Put a collection directory in a shared repository so your team can review, version, and reuse DynamoDB requests with its existing Git workflow.
Start with version control
Read Version Control to connect a collection to a repository and understand which Dynomate files it contains.
Use version control
Use branches and pull requests to review changes to shared requests before they reach the main branch. A diff can show changes to operations, table references, expressions, and request variables.
Dynomate watches collection directories and reloads valid request files after an external change. Git actions, including commit, push, pull, and conflict resolution, remain in your Git client.
Follow the complete workflow in Use Dynomate collections with version control.
Coordinate changes
- Pull current changes before you edit a shared request.
- Use a branch when a request change needs review.
- Avoid editing the same request file at the same time.
- Save the open request before you review its Git diff.
- Resolve conflicts in your Git client, then validate the request in Dynomate.
Dynomate keeps unsaved editor changes when the file changes outside the app. Save or discard the draft, then reopen the request if the tab shows an older version.
Protect environment values
Review collection environment files and request variables before you commit them. A value marked as secret is masked in the Dynomate editor, but its local file still contains the value.
Do not commit credentials, tokens, or other sensitive values. Use Variables to separate reusable request structure from values that change between users and environments.