Add Auggie workflow files for AI-assisted development#1
Add Auggie workflow files for AI-assisted development#1sharath333 wants to merge 1 commit intomainfrom
Conversation
Add 6 GitHub Actions workflow files that call reusable workflows from the augment-solutions/.github org: - auggie-implement-direct.yml: Direct implementation from issues - auggie-plan.yml: Implementation plan generation for issues - auggie-pr-review.yml: AI-powered PR review - auggie-spec.yml: Technical spec generation for issues - auggie-test-generate.yml: Test generation for PRs - auggie-triage.yml: Build failure triage Each workflow includes proper trigger conditions (labels/slash commands), progress tracking via labels and reactions, and calls the corresponding org-level reusable workflow with AUGMENT_SESSION_AUTH secret.
|
Code Review Triage 🛡️ · Requires Review Recommendation: 👉 Start Assisted ReviewWhat happens in the Assisted Review?This link launches a collaborative AI-human code review that walks through:
JustificationThis PR adds 6 new GitHub Actions workflow files under Reach out to #feedback-code-review-agent for feedback |
![augment-app-staging[bot]](https://avatars.githubusercontent.com/in/1008152?s=60&v=4){kind=small}
| if: github.event.issue.pull_request != null | ||
| runs-on: ubuntu-latest | ||
| permissions: | ||
| pull-requests: write |
There was a problem hiding this comment.
github.rest.reactions.createForIssueComment uses the issues-comments API, but this job’s permissions only include pull-requests: write, so the reaction call may be denied at runtime. Same applies to the post-review-comment job and the workflow-level permissions block.
Severity: medium
Other Locations
.github/workflows/auggie-pr-review.yml:21.github/workflows/auggie-pr-review.yml:93
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
|
|
||
| permissions: | ||
| contents: write | ||
| pull-requests: write |
There was a problem hiding this comment.
This workflow calls github.rest.reactions.createForIssueComment, which typically requires issues: write, but the workflow/job permissions only grant pull-requests: write. That can cause the reaction steps to fail even when the trigger matches.
Severity: medium
Other Locations
.github/workflows/auggie-test-generate.yml:28.github/workflows/auggie-test-generate.yml:99
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| const issue = context.payload.issue; | ||
|
|
||
| // Get all comments | ||
| const comments = await github.rest.issues.listComments({ |
There was a problem hiding this comment.
The comment says “Get all comments”, but issues.listComments is paginated and this call only returns the first page, so longer issues may lose context in issue_comments. Also, passing the full concatenated comment bodies via step/job outputs can hit GitHub Actions output size limits on large threads.
Severity: medium
Other Locations
.github/workflows/auggie-plan.yml:85
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| # | ||
| # SETUP REQUIRED: | ||
| # - Add AUGMENT_SESSION_AUTH secret to your repository | ||
| # - Add GH_TOKEN secret (GitHub token with repo and workflow permissions) |
There was a problem hiding this comment.
The header says a GH_TOKEN secret is required, but the workflow actually passes ${{ secrets.GITHUB_TOKEN }} to gh_token, which is contradictory for setup docs. This may confuse users configuring the workflow.
Severity: low
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| if: github.event.issue.pull_request != null | ||
| runs-on: ubuntu-latest | ||
| permissions: | ||
| pull-requests: write |
There was a problem hiding this comment.
In .github/workflows/auggie-pr-review.yml line 29, this job calls reactions.createForIssueComment, but that endpoint requires issues: write rather than only pull-requests: write. The first slash-command comment will therefore 403 in check-comment and the reusable PR review never starts.
Severity: high
Other Locations
.github/workflows/auggie-pr-review.yml:93.github/workflows/auggie-test-generate.yml:28.github/workflows/auggie-test-generate.yml:99
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| fi | ||
|
|
||
| # Check if triggered by slash command | ||
| if [ "$EVENT_NAME" = "issue_comment" ]; then |
There was a problem hiding this comment.
In .github/workflows/auggie-implement-direct.yml line 51, issue_comment also fires for pull requests, but this branch never excludes context.payload.issue.pull_request. A /auggieImplementDirect comment on a PR conversation will therefore run the issue-only implementation flow against PR metadata instead of a GitHub issue.
Severity: medium
Other Locations
.github/workflows/auggie-plan.yml:65.github/workflows/auggie-spec.yml:70
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| const issue = context.payload.issue; | ||
|
|
||
| // Get all comments | ||
| const comments = await github.rest.issues.listComments({ |
There was a problem hiding this comment.
In .github/workflows/auggie-implement-direct.yml line 120, github.rest.issues.listComments() only returns the first page by default, so issue_comments drops everything after the 30th comment. Long-running issues would send incomplete requirements/history to the implementation workflow.
Severity: medium
Other Locations
.github/workflows/auggie-plan.yml:85
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
1 participant
Summary
Adds 6 GitHub Actions workflow files that call reusable workflows from the
augment-solutions/.githuborg for AI-assisted development.Workflows Added
auggie-implement-direct.ymlauggieImplementDirector/auggieImplementDirectcommentauggie-plan.ymlauggieImplementPlanor/auggieImplementPlancommentauggie-pr-review.yml/auggiePRReviewcomment on PRsauggie-spec.ymlauggieSpecor/auggieApproveSpeccommentauggie-test-generate.yml/auggieTestGeneratecomment on PRsauggie-triage.ymlPrerequisites
AUGMENT_SESSION_AUTHsecret must be configured in repository settingsaugment-solutions/.githuborgCustomizations for OpenSearch
auggie-plan.ymlandauggie-spec.ymlinclude OpenSearch-specific context incustom_instructions(Java/Gradle codebase, backward compatibility requirements, unit test expectations)Pull Request opened by Augment Code with guidance from the PR author