Skip to content

Disposable reviewer-bot epoch flip PR comment retest 2#538

Closed
PLeVasseur wants to merge 1 commit intomainfrom
validation/epoch-flip-20260320-final-pr-comment-retest-2
Closed

Disposable reviewer-bot epoch flip PR comment retest 2#538
PLeVasseur wants to merge 1 commit intomainfrom
validation/epoch-flip-20260320-final-pr-comment-retest-2

Conversation

@PLeVasseur
Copy link
Copy Markdown
Collaborator

Disposable same-repo PR for reviewer-bot post-fix assignment retest. Do not merge; retire after validation.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 20, 2026

Deploy Preview for scrc-coding-guidelines ready!

Name Link
🔨 Latest commit e8dfbbe
🔍 Latest deploy log https://app.netlify.com/projects/scrc-coding-guidelines/deploys/69bdc52c390b2f00082f2331
😎 Deploy Preview https://deploy-preview-538--scrc-coding-guidelines.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@PLeVasseur
Copy link
Copy Markdown
Collaborator Author

@guidelines-bot /r? @felix91gr

@github-actions github-actions bot requested a review from felix91gr March 20, 2026 22:08
@github-actions
Copy link
Copy Markdown
Contributor

👋 Hey @felix91gr! You've been assigned to review this coding guideline PR.

Your Role as Reviewer

As outlined in our contribution guide, please:

  1. Begin your review within 14 days
  2. Provide constructive feedback on the guideline content, examples, and formatting
  3. Iterate with @PLeVasseur - they may update the PR based on your feedback
  4. When the guideline is ready, approve and add to the merge queue

Review Checklist

  • Guideline title is clear and follows conventions
  • Amplification section expands on the title appropriately
  • Rationale explains the "why" effectively
  • Non-compliant example(s) clearly show the problem
  • Compliant example(s) clearly show the solution
  • Code examples compile (check the CI results)
  • FLS paragraph ID is correct

Bot Commands

If you need to pass this review:

  • @guidelines-bot /pass [reason] - Pass just this PR to the next reviewer
  • @guidelines-bot /away YYYY-MM-DD [reason] - Step away from the queue until a date
  • @guidelines-bot /release [@username] [reason] - Release assignment (yours or someone else's with triage+ permission)

To assign someone else:

  • @guidelines-bot /r? @username - Assign a specific reviewer
  • @guidelines-bot /r? producers - Request the next reviewer from the queue

Other commands:

  • @guidelines-bot /claim - Claim this review for yourself
  • @guidelines-bot /rectify - Reconcile this issue/PR review state from GitHub
  • @guidelines-bot /label +label-name - Add a label
  • @guidelines-bot /label -label-name - Remove a label
  • @guidelines-bot /queue - Show reviewer queue
  • @guidelines-bot /commands - Show all available commands

@github-actions
Copy link
Copy Markdown
Contributor

@felix91gr has been assigned as reviewer.

@github-actions github-actions bot added the status: awaiting reviewer response Reviewer-bot is waiting on reviewer freshness or current-head review label Mar 20, 2026
@PLeVasseur
Copy link
Copy Markdown
Collaborator Author

@guidelines-bot /r? @AlexCeleste

@github-actions github-actions bot removed the request for review from felix91gr March 20, 2026 22:09
@github-actions
Copy link
Copy Markdown
Contributor

👋 Hey @AlexCeleste! You've been assigned to review this coding guideline PR.

Your Role as Reviewer

As outlined in our contribution guide, please:

  1. Begin your review within 14 days
  2. Provide constructive feedback on the guideline content, examples, and formatting
  3. Iterate with @PLeVasseur - they may update the PR based on your feedback
  4. When the guideline is ready, approve and add to the merge queue

Review Checklist

  • Guideline title is clear and follows conventions
  • Amplification section expands on the title appropriately
  • Rationale explains the "why" effectively
  • Non-compliant example(s) clearly show the problem
  • Compliant example(s) clearly show the solution
  • Code examples compile (check the CI results)
  • FLS paragraph ID is correct

Bot Commands

If you need to pass this review:

  • @guidelines-bot /pass [reason] - Pass just this PR to the next reviewer
  • @guidelines-bot /away YYYY-MM-DD [reason] - Step away from the queue until a date
  • @guidelines-bot /release [@username] [reason] - Release assignment (yours or someone else's with triage+ permission)

To assign someone else:

  • @guidelines-bot /r? @username - Assign a specific reviewer
  • @guidelines-bot /r? producers - Request the next reviewer from the queue

Other commands:

  • @guidelines-bot /claim - Claim this review for yourself
  • @guidelines-bot /rectify - Reconcile this issue/PR review state from GitHub
  • @guidelines-bot /label +label-name - Add a label
  • @guidelines-bot /label -label-name - Remove a label
  • @guidelines-bot /queue - Show reviewer queue
  • @guidelines-bot /commands - Show all available commands

@github-actions github-actions bot requested a review from AlexCeleste March 20, 2026 22:09
@github-actions
Copy link
Copy Markdown
Contributor

@AlexCeleste has been assigned as reviewer (previously: @felix91gr).

@PLeVasseur
Copy link
Copy Markdown
Collaborator Author

Retiring disposable post-fix assignment retest PR.

@PLeVasseur PLeVasseur closed this Mar 20, 2026
@PLeVasseur PLeVasseur deleted the validation/epoch-flip-20260320-final-pr-comment-retest-2 branch March 20, 2026 22:12
@github-actions github-actions bot removed the status: awaiting reviewer response Reviewer-bot is waiting on reviewer freshness or current-head review label Mar 20, 2026
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