fix: dim labels and reposition note for webhook-driven readonly fields

[R-Hart80]

Closes #5

Problem

When isWebhookDriven is true, the four GitHub-integration input fields (repo_owner, repo_name, branch, git_ontology_path) were already rendered with readOnly and cursor-not-allowed opacity-60 on the inputs themselves. However, their labels remained at full opacity, which was visually inconsistent — the fields looked disabled but the labels did not.

Additionally, the explanatory note "Repository fields are managed by the GitHub integration." was placed between the first two-column grid (repo owner + name) and the second grid (branch + file path), making it ambiguous whether it applied to all four fields or only the bottom two.

Changes

• app/projects/[id]/settings/page.tsx
  • Added isWebhookDriven && "opacity-60" to the className of all four field labels so they dim in sync with their inputs.
  • Moved the explanatory note to appear after both field grids so it clearly covers all four read-only fields as a group.

Test plan

• Open a project that has a GitHub webhook configured (isWebhookDriven === true).
• Navigate to Settings → GitHub Integration.
• Verify the four labels ("Repository owner", "Repository name", "Branch", "File path") are visually dimmed (opacity-60) alongside their inputs.
• Verify the note "Repository fields are managed by the GitHub integration." appears below all four fields, not between them.
• Open a project without GitHub integration — verify labels are full opacity and inputs are editable.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@R-Hart80 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 44 minutes and 33 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6a5a1c2d-2c08-49e4-a1da-0636d9938d76

📥 Commits

Reviewing files that changed from the base of the PR and between 0233a83 and 1e51ffb.

📒 Files selected for processing (1)

• app/projects/[id]/settings/page.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!