-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat(API): Add Repo Sync [TSI-1923] #569
Conversation
paths/repo_syncs/events.yaml
Outdated
description: |- | ||
Get the history of a single Repo Sync. The history includes all imports and exports | ||
performed by the Repo Sync. | ||
operationId: repo_sync/history |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we call this repo_sync/events
to align it with the endpoint name?
paths/repo_syncs/index.yaml
Outdated
--- | ||
summary: Get Repo Syncs | ||
description: Lists all Repo Syncs from an account | ||
operationId: repo_sync/index |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think our convention is to list list
as the operation id for the index endpoint
paths/repo_syncs/index.yaml
Outdated
-u USERNAME_OR_ACCESS_TOKEN | ||
- lang: CLI v2 | ||
source: |- | ||
phrase repo_sync index \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be list
😅
Add unified Repo Sync API