Repository action reference

The vcs domain is the repository-native surface for GitHub, GitLab, and Bitbucket. It complements the higher-level integration search: use integrations to retrieve connected product knowledge, and use VCS when the request is about a repository object, diff, review, notification, link, automation, webhook, or ingest operation.

Provider values

Use repo_ref for a complete path such as owner/repo or group/subgroup/repo. The separate owner and repo fields are convenient for simple two-segment paths.

Repository and project actions

Project-linking calls use project_id or project_name; import flows can also use description, create_project, ingest, and sync_config. Removing a repository connection and deleting the upstream repository are different operations: confirm the live schema and result before any destructive call.

Pull request actions

Use number for the pull request. review_pull accepts an event of APPROVE, REQUEST_CHANGES, or COMMENT, a review body, and optional inline comments. merge_pull accepts merge, squash, or rebase through merge_method, plus optional commit title and message fields.

Reviews, comments, and merges change the upstream provider. A read-only code review should stop before those actions unless the user explicitly asks to publish or merge.

Issue actions

Issue writes use title, body, labels, and assignees as applicable. These are provider issues, not native ContextStream entity(kind="ticket", …) records.

Commits, refs, and files

Use sha for a commit, base and head for comparisons, ref_name for a branch/tag/commit selector, and path for a tree or blob path. Provider code search and ContextStream's indexed search domain are different: provider search sees the linked remote state, while ContextStream search is optimized for grounded work across the indexed project.

Activity and notifications

Notification mutation uses notification_id. Treat “mark all” as an explicit write; do not run it merely to inspect the inbox.

Links, automations, and webhooks

Links use source_type, source_id, target_type, and target_id; deletion uses link_id. Automations use automation_id and automation_config. Webhook registration and removal use the repository identity plus the optional provider selector; the consolidated call exposes no callback-URL or secret field.

Filters and pagination

Common selectors include provider, workspace_id, repo_ref (or owner/repo), state, branch, and query. Lists use page and per_page; code search can also use limit. search_vcs accepts scope such as code, issues, or pull requests. sync_repo accepts full for a full refresh. Preserve the same repository, provider, state, and branch filters while paging.

The action enum is unified, but provider permissions and feature support still apply. A valid action can return an authorization or provider-capability error for a particular connection. Do not silently fall back to a different provider or repository.

Complete input field map

The schema is consolidated, so the presence of a field does not mean every action consumes it. Use the action sections above and the live schema annotations together.