Skip to content

feat(frontend): add GitHub sync events panel#68

Merged
JustAGhosT merged 1 commit into
mainfrom
feat/github-sync-events-panel
Jul 12, 2026
Merged

feat(frontend): add GitHub sync events panel#68
JustAGhosT merged 1 commit into
mainfrom
feat/github-sync-events-panel

Conversation

@JustAGhosT

Copy link
Copy Markdown
Collaborator

Summary

  • add typed frontend API methods for GitHub sync event listing and retries
  • show inbound webhook and outbound GitHub event summaries in Project Settings
  • allow retrying failed sync events individually or as a failed-event sweep

Baton

  • Follow-up for task 3fa7cb6a: admin visibility/retry for failed gh_outbound_events and unprocessed gh_webhook_deliveries.

Validation

  • frontend tsc
  • vite build

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JustAGhosT, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 48e8d2eb-8b8d-4fa8-9b10-cb067a583edf

📥 Commits

Reviewing files that changed from the base of the PR and between 2c6bb08 and 43868a6.

📒 Files selected for processing (3)
  • frontend/src/api.ts
  • frontend/src/components/ProjectSettings.tsx
  • frontend/src/types.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/github-sync-events-panel

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

Comment @coderabbitai help to get the list of available commands.

@JustAGhosT JustAGhosT merged commit c6f780c into main Jul 12, 2026
3 checks passed
@JustAGhosT JustAGhosT deleted the feat/github-sync-events-panel branch July 12, 2026 13:55

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 43868a67b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

{!row.processed && (
<button
onClick={onRetry}
disabled={busy}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Disable all row retries while one is in flight

When an admin starts one row retry, only that row is disabled. Because busyId is global, clicking a different row changes it and re-enables the first button while its request may still be in flight; a second click can send two concurrent retries for the same webhook delivery. The backend processGithubDelivery selects processed = false and marks processed only after applying the payload, so overlapping manual retries can duplicate sync side effects/activity. Disable every row retry whenever busyId !== null or track per-row in-flight state.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant