Appearance
Permissions
Verdog uses your GitHub account to sign you in and check repository access. Published workflows follow their source repository's permissions: public workflows are visible to signed-in catalogue users, and private workflows are visible when the signed-in account and its authorization can read the repository.
Account access
Catalogue features require a Verdog account session associated with your GitHub identity. Sign in through VS Code's built-in GitHub authentication. This session is separate from your local Git credentials and agent provider authentication.
No Verdog GitHub App registration or installation is required. Standard sign-in provides identity and access to public repository metadata. Private catalogue entries also require authorization that can access their source repository. Choose Verdog: Authorize Private Repository Access to request this explicitly. GitHub's repo scope grants broad read and write repository access; the extension explains that scope before requesting authorization. Cancelling leaves the current access mode unchanged.
Verdog: Use Public Catalogue Access returns to the standard sign-in mode. It does not revoke GitHub authorizations or other existing sessions. Manage those through GitHub and VS Code's account controls. Your local Git credentials are used separately when fetching workflow source.
Repository permissions
| Operation | Required permission |
|---|---|
| Read a restricted catalogue entry | Read access to its repository |
| Publish a release | Maintain or Admin access, and a Verdog seat |
| Retract a release | Maintain or Admin access |
Use Verdog: Show My Access in the Command Palette to check your access.
Write access alone does not allow publication. Local edits do not require GitHub repository authorization. Generation, analysis, hosted checks, and renaming require neither sign-in nor a Verdog seat: you submit the project data directly for processing. This also applies to generation during New Project and catalogue imports.
Sharing and access changes
Users whose GitHub authorization can read a private or internal repository can discover its published workflows. Manage collaborators and repository visibility in GitHub; there is no separate catalogue sharing list. Verdog checks current GitHub permissions when you access published workflows.
If a workflow is missing from the catalogue, check that you can read its repository and that your sign-in authorization allows access to it. Entries you cannot access are omitted from listings. Expired authorization produces a sign-in error; temporary GitHub failures produce an availability error rather than an empty catalogue.
Each Verdog session retains the GitHub authorization supplied for its own sign-in. Signing in elsewhere does not change that session's repository access. Repository tokens retain the authorization used when they were created and remain independent of the issuing session's logout. If GitHub revokes or expires that authorization, sign in again and create a replacement repository token. Repository permissions are still checked live on every request.
After renaming or transferring a repository, republish its workflows to update their catalogue repository name.
What is sent to Verdog
Generation, hosted checks, and renaming send project manifests and declared source files, including authored text files and pinned dependencies, to Verdog for processing. Generation runs after structural canvas edits and during project creation and catalogue imports. In trusted VS Code workspaces, opening or refreshing a graph automatically sends project manifests, including pinned dependency manifests, for termination analysis. Restricted Mode disables automatic analysis until Workspace Trust is granted.
The service does not retain a project workspace or source snapshot. Fetching workflow source and its Git dependencies happens directly between your machine and GitHub using your credentials.
Publishing stores the repository, commit, workflow identifier, package, description, graph preview, declared dependencies and environment requirements, and publication metadata in the catalogue. README text and Python input and output type schemas are not stored there.
Verdog also retains account and sign-in records, session-specific GitHub authorization tokens, repository-token authorizations, and audit events. These GitHub tokens are used to check current repository permissions.