Conversation
Chore sync 1.8.0 into main
Create workflow to auto add labels to issues
Co-authored-by: stnguyen90 <[email protected]>
Co-authored-by: stnguyen90 <[email protected]>
Add GitHub AI Moderator workflow
…triage.md-5094 Add agentic workflow issue-triage
Co-authored-by: stnguyen90 <[email protected]>
Add missing models: read permission to AI Moderator workflow
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
📝 WalkthroughWalkthroughThis PR adds infrastructure and configuration to support automated issue management workflows. Changes include: adding a gitattributes rule to treat generated lock workflow files as generated content with "ours" merge strategy; introducing comprehensive label mappings in Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
Security Scan Results for PRDocker Image Scan Results
Source Code Scan Results🎉 No vulnerabilities found! |
✨ Benchmark results
⚡ Benchmark Comparison
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.github/workflows/issue-triage.md (1)
24-78: Triage documentation is comprehensive; minor grammar refinements recommended.The documentation is well-structured and clearly guides the agentic workflow through analysis, labeling, and commenting. Three minor grammar/style issues are flagged by static analysis (all valid per English grammar conventions):
- Line 28: Capitalize "GitHub" (currently "github")
- Line 32: Use hyphen for compound adjective: "one-sentence analysis" (currently "one sentence")
- Line 78: Capitalize proper noun: "GitHub Markdown" (currently "GitHub markdown")
Apply these diffs to address the grammar and style issues:
-You're a triage assistant for GitHub issues. Your task is to analyze issue #${{ github.event.issue.number }} and perform some initial triage tasks related to that issue. +You're a triage assistant for GitHub issues. Your task is to analyze issue #${{ github.event.issue.number }} and perform some initial triage tasks related to that issue.-2. Retrieve the issue content using the `get_issue` tool. If the issue is obviously spam, or generated by bot, or something else that is not an actual issue to be worked on, then add an issue comment to the issue with a one sentence analysis and exit the workflow. +2. Retrieve the issue content using the `get_issue` tool. If the issue is obviously spam, or generated by bot, or something else that is not an actual issue to be worked on, then add an issue comment to the issue with a one-sentence analysis and exit the workflow.- - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. + - Use collapsed-by-default sections in the GitHub Markdown to keep the comment tidy. Collapse all sections except the short main summary at the top.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
.gitattributes(1 hunks).github/labeler.yml(1 hunks).github/workflows/ai-moderator.yml(1 hunks).github/workflows/auto-label-issue.yml(1 hunks).github/workflows/issue-triage.md(1 hunks)README.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
.github/workflows/issue-triage.md
[uncategorized] ~28-~28: The official name of this software platform is spelled with a capital “H”.
Context: ...ues. Your task is to analyze issue #${{ github.event.issue.number }} and perform some ...
(GITHUB)
[grammar] ~32-~32: Use a hyphen to join words.
Context: ...an issue comment to the issue with a one sentence analysis and exit the workflow....
(QB_NEW_EN_HYPHEN)
[uncategorized] ~78-~78: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...apsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all ...
(MARKDOWN_NNP)
🔇 Additional comments (5)
.gitattributes (1)
9-9: Well-structured merge strategy for generated workflow files.The new
.lock.ymlrule appropriately marks generated workflow artifacts and uses theoursmerge strategy to prevent merge conflicts on auto-generated content. This is a sensible safeguard for syncing between branches.README.md (1)
1-1: Announcement update is clear and properly formatted.The link to the Transactions API announcement is valid and the text is accurate. The change aligns with the broader documentation refresh.
.github/labeler.yml (1)
1-83: Label mappings are comprehensive and well-organized.The configuration covers all major Appwrite product areas with relevant keyword patterns. Commented sections (docs, platform, cloud) provide room for future expansion. The regex patterns are specific enough to avoid over-labeling while capturing relevant issue keywords.
.github/workflows/issue-triage.md (1)
1-23: Agentic triage workflow is well-configured with sensible defaults.The YAML frontmatter is valid and the configuration choices are reasonable: the 30-day expiration window prevents stale automation, read-all permissions are safe, and the 5-label cap prevents over-labeling. The integration with githubnext/agentics is a solid pattern for AI-assisted workflows.
.github/workflows/ai-moderator.yml (1)
1-32: AI Moderator workflow is well-configured with appropriate permissions and current version pinning.The workflow covers all relevant event types for content moderation (issues, comments, PRs, discussions) and permissions are properly scoped. The v1 tag is current and points to v1.1.4 (Oct 26, 2025), so using github/ai-moderator@v1 will use the latest v1.x release. This approach follows the recommended pattern and is actively maintained.
| name: Auto Label Issue | ||
|
|
||
| on: | ||
| issues: | ||
| types: [opened] | ||
|
|
||
| permissions: | ||
| issues: write | ||
| contents: read | ||
|
|
||
| jobs: | ||
| labeler: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Issue Labeler | ||
| uses: github/[email protected] | ||
| with: | ||
| configuration-path: .github/labeler.yml | ||
| enable-versioned-regex: false | ||
| include-title: 1 | ||
| env: |
There was a problem hiding this comment.
🧩 Analysis chain
Auto-label workflow is properly scoped and configured.
The workflow correctly triggers only on newly opened issues, uses minimal permissions, and properly references the labeler configuration. Disabling versioned-regex and including the title in analysis are sensible defaults.
Please verify that github/[email protected] is the appropriate version. Check if there are newer versions available and whether v3.4 is still actively maintained:
🌐 Web query:
What is the latest version of github/issue-labeler action and what changed in recent versions?
💡 Result:
Latest published release: actions/labeler v6.0.1 (tag v6.0.1, published Sep 4). [1]
Recent notable changes
- v6.0.1 — minor update: upgraded publish-action from 0.2.2 → 0.4.0. [1]
- v6.0.0 — added workflow to publish immutable action package; upgraded Node.js runtime to v24 (runners must be v2.327.1+); multiple dependency upgrades. [1]
- v5.0.0 — breaking redesign of the labeler config (expanded match object, branch-name matching added), fixed sync-labels input bug, default dot input set to true, runtime moved to Node.js 20. [1]
Source: actions/labeler releases page. [1]
References
[1] actions/labeler — Releases (GitHub). (github.com)
Citations:
Critical issue: Action reference appears incorrect and severely outdated.
The workflow references github/[email protected], but the official GitHub Action is actions/labeler at version v6.0.1 (latest released Sep 4). The namespace github/issue-labeler does not match any current official action, and v3.4 is significantly behind current versions.
Additionally, v5.0.0 introduced breaking changes to the labeler config format, so any upgrade requires careful config review.
Actions required:
- Verify the correct action namespace and verify if
github/issue-labelerstill exists or is maintained - Update to
actions/labelerwith an appropriate version, likely v6 or v5 depending on config compatibility - Ensure
.github/labeler.ymlconfiguration matches the target version's expected format
🤖 Prompt for AI Agents
.github/workflows/auto-label-issue.yml lines 1-21: the workflow references an
incorrect/outdated action namespace `github/[email protected]`; replace the
action with the official `actions/labeler` at a compatible version (e.g.,
actions/labeler@v6 or @v5 depending on config), update the uses line
accordingly, and then validate and adjust .github/labeler.yml to the chosen
version's config schema (v5+ has breaking schema changes) before committing.
What does this PR do?
Update 1.8.x with what's in main.
Test Plan
Automated tests should pass
Related PRs and Issues
None
Checklist