tasks

Team routing rules that steer agent repo selection (RepoRoutingRule).

The same rows the Slack /posthog rules commands manage; the repo selection agent reads them ordered by priority when picking a repository for a task. Rules whose repository is not connected to the project are ignored at selection time, so a stale rule is inert rather than harmful — which is why writes here don't check the connected-repository list (the UI constrains the picker to connected repos anyway).

get/api/projects/{project_id}/tasks/repo_routing_rules/{id}/

Request

  • Base URL: https://us.posthog.com
  • URL: https://us.posthog.com/api/projects/{project_id}/tasks/repo_routing_rules/{id}/
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

idstring uuid required

A UUID string identifying this repo routing rule.

project_idstring required

Project ID of the project you're trying to access. To find the ID of the project, make a call to /api/projects/.

Response

idstring uuid required
rule_textstring required

Plain-text description of the requests that should route to the repository, e.g. 'anything about the internal dashboard'. At most 300 characters.

repositorystring required

Target repository as owner/repo, e.g. 'posthog/posthog.com'.

priorityinteger required
created_atstring date-time required
updated_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.