Skip to content

Add GitHub Actions workflow to manage agentkit-challenge PR reviews#114

Merged
amanintech merged 2 commits intomainfrom
copilot/review-agentkit-challenge-prs
Mar 29, 2026
Merged

Add GitHub Actions workflow to manage agentkit-challenge PR reviews#114
amanintech merged 2 commits intomainfrom
copilot/review-agentkit-challenge-prs

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 29, 2026

Automates CodeRabbit review enforcement across all open agentkit-challenge PRs: triggers missing/stale reviews, posts author reminders for unresolved feedback, and surfaces a categorized job summary.

Changes

  • .github/workflows/review-challenge-prs.yml — new workflow that:
    • Scans all open PRs labeled agentkit-challenge
    • Posts @coderabbitai review for PRs with no review or where commits are newer than the last review (stale)
    • Comments on PRs with CodeRabbit CHANGES_REQUESTED asking the author to resolve before maintainer review
    • Comments on PRs with unresolved actionable CodeRabbit comments (COMMENTED state)
    • Deduplicates reminders via embedded HTML markers (<!-- agentkit-review-bot: ... -->)
    • Emits a job summary categorizing PRs into: triggered, changes-requested, actionable-pending, clean
    • Runs on schedule (M/W/F 09:00 UTC) and via workflow_dispatch with optional dry-run

Current state of agentkit-challenge PRs (as of 2026-03-29)

Status PRs
🔴 CodeRabbit CHANGES_REQUESTED #113, #110, #109, #86, #84
🔄 No CodeRabbit review (will be triggered) #106
🟡 Actionable comments pending #107, #105, #104, #102, #101, #100, #99, #98, #97, #95, #93, #92, #91, #90, #88, #87, #80, #78, #72, #70, #69, #50, #36

PR Checklist

1. Select Contribution Type

  • Kit (kits/<category>/<kit-name>/)
  • Bundle (bundles/<bundle-name>/)
  • Template (templates/<template-name>/)

2. General Requirements

  • PR is for one project only (no unrelated changes)
  • No secrets, API keys, or real credentials are committed
  • Folder name uses kebab-case and matches the flow ID
  • All changes are documented in README.md (purpose, setup, usage)

3. File Structure (Check what applies)

  • config.json present with valid metadata (name, description, tags, steps, author, env keys)
  • All flows in flows/<flow-name>/ (where applicable) include:
    • config.json (Lamatic flow export)
    • inputs.json
    • meta.json
    • README.md
  • .env.example with placeholder values only (kits only)
  • No hand‑edited flow config.json node graphs (changes via Lamatic Studio export)

4. Validation

  • npm install && npm run dev works locally (kits: UI runs; bundles/templates: flows are valid)
  • PR title is clear (e.g., [kit] Add <name> for <use case>)
  • GitHub Actions workflows pass (all checks are green)
  • All CodeRabbit or other PR review comments are addressed and resolved
  • No unrelated files or projects are modified

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com/graphql
    • Triggering command: /usr/bin/gh gh auth status (http block)
  • https://api.github.com/user
    • Triggering command: /usr/bin/curl curl -s -H Authorization: ****** REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:


💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

Copilot AI changed the title [WIP] Review open PRs labeled agentkit-challenge Add GitHub Actions workflow to manage agentkit-challenge PR reviews Mar 29, 2026
Copilot AI requested a review from amanintech March 29, 2026 22:08
@amanintech amanintech marked this pull request as ready for review March 29, 2026 22:18
@amanintech amanintech merged commit 4d361bd into main Mar 29, 2026
3 checks passed
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.

2 participants