Problem
In Project Settings → Upstream Source Tracking, when the sync config is webhook-driven (isWebhookDriven === true), the four GitHub-integration fields render read-only:
| Grid |
Fields |
First grid-cols-2 |
Repository owner, Repository name |
Second grid-cols-2 |
Branch, File path |
The explanatory note — "Repository fields are managed by the GitHub integration." — is rendered between the two grids.
Because it sits mid-group, it reads ambiguously: a user can't tell whether it captions the two fields above it, the two below it, or all four. All four are in fact webhook-managed.
Expected
The note should appear after both grids, so it unambiguously captions the whole group of four read-only fields.
Location
app/projects/[id]/settings/page.tsx — RemoteSyncSection, the isWebhookDriven && <p>…</p> block.
Notes
Related
Problem
In Project Settings → Upstream Source Tracking, when the sync config is webhook-driven (
isWebhookDriven === true), the four GitHub-integration fields render read-only:grid-cols-2grid-cols-2The explanatory note — "Repository fields are managed by the GitHub integration." — is rendered between the two grids.
Because it sits mid-group, it reads ambiguously: a user can't tell whether it captions the two fields above it, the two below it, or all four. All four are in fact webhook-managed.
Expected
The note should appear after both grids, so it unambiguously captions the whole group of four read-only fields.
Location
app/projects/[id]/settings/page.tsx—RemoteSyncSection, theisWebhookDriven && <p>…</p>block.Notes
Refs #5. Verify: read-only upstream sync fields when webhook-driven #5 is a verification issue whose checklist is already fully ticked, so it isn't the right home for this defect — hence this issue.opacity-60; that part was reverted as a WCAG AA contrast regression (~9.3:1 → ~3.35:1 on normal-size text) and is not part of this issue.Related