Context
Commit 57435cb (with companion backend commit 3800304 on ontokit-api) introduced automatic upstream sync configuration when GitHub webhooks are enabled.
What was added
Backend (ontokit-api 3800304):
- When webhooks are enabled on a GitHub integration, an
UpstreamSyncConfig is automatically created (or updated) with frequency="webhook", using the integration's repo_owner, repo_name, default_branch, and ontology_file_path. This eliminates the need for users to manually fill out the Upstream Source Tracking form with the same information.
- When webhooks are disabled, the upstream sync frequency is downgraded from
"webhook" to "manual" (the config is preserved so the user's update_mode preference is kept).
Frontend (ontokit-web 57435cb):
- In the configured (non-editing) view: a note reading "Automatically triggered by GitHub webhooks" appears below the frequency label when the config is webhook-driven.
- In the editing form: the repo owner, repo name, branch, and file path fields become read-only with dimmed styling and a note "Repository fields are managed by the GitHub integration." These values are derived from the GitHub integration and shouldn't be edited independently.
- The frequency dropdown and update mode remain fully editable.
Test checklist
Context
Commit
57435cb(with companion backend commit3800304on ontokit-api) introduced automatic upstream sync configuration when GitHub webhooks are enabled.What was added
Backend (ontokit-api
3800304):UpstreamSyncConfigis automatically created (or updated) withfrequency="webhook", using the integration'srepo_owner,repo_name,default_branch, andontology_file_path. This eliminates the need for users to manually fill out the Upstream Source Tracking form with the same information."webhook"to"manual"(the config is preserved so the user'supdate_modepreference is kept).Frontend (ontokit-web
57435cb):Test checklist
frequency="webhook""manual"