Skip to content

Commit 5cb588f

Browse files
committed
agentics fixes
1 parent 8050b5b commit 5cb588f

17 files changed

+53
-193
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ A sample family of reusable [GitHub Agentic Workflows](https://github.github.com
1515
### Research, Status & Planning Workflows
1616

1717
- [📚 Weekly Research](docs/weekly-research.md) - Collect research updates and industry trends
18-
- [👥 Daily Team Status](docs/daily-team-status.md) - Assess repository activity and create status reports
18+
- [👥 Daily Repo Status](docs/daily-repo-status.md) - Assess repository activity and create status reports
1919
- [📋 Daily Plan](docs/daily-plan.md) - Update planning issues for team coordination
2020
- [📋 Plan Command](docs/plan.md) - Break down issues into actionable sub-tasks with /plan command
2121

TODO.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The agentic workflows have been updated to use GitHub Discussions instead of Iss
99
- **Description**: Important updates and status reports for the project
1010
- **Used by workflows**:
1111
- daily-plan.md
12-
- daily-team-status.md
12+
- daily-repo-status.md
1313
- daily-dependency-updates.md
1414

1515
### 2. Ideas

docs/ci-doctor.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,12 @@ The [CI Doctor workflow](../workflows/ci-doctor.md?plain=1) monitors your GitHub
1111
gh extension install github/gh-aw
1212

1313
# Add the CI Doctor workflow to your repository
14-
gh aw add githubnext/agentics/ci-doctor --pr
14+
gh aw add githubnext/agentics/ci-doctor
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
17+
This walks you through adding the workflow to your repository.
1818

19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR, the workflow will automatically trigger when monitored CI workflows fail. You cannot start this workflow manually as it responds to workflow failure events.
19+
After adding, the workflow will automatically trigger when monitored CI workflows fail. You cannot start this workflow manually as it responds to workflow failure events.
2220

2321
**Mandatory Checklist**
2422

docs/daily-accessibility-review.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,23 +11,13 @@ The [daily accessibility review workflow](../workflows/daily-accessibility-revie
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily Accessibility Review workflow to your repository
14-
gh aw add githubnext/agentics/daily-accessibility-review --pr
14+
gh aw add githubnext/agentics/daily-accessibility-review
1515
```
1616

17-
This creates an issue in your repository recording accessibility problems found.
18-
19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
22-
23-
```bash
24-
gh aw run daily-accessibility-review
25-
```
17+
This walks you through adding the workflow to your repository.
2618

2719
**Mandatory Checklist**
2820

29-
* [ ] I understand that, by default, the agentic portion of this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
30-
3121
* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
3222

3323
## Configuration

docs/daily-dependency-updates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@ The [daily dependency updater workflow](../workflows/daily-dependency-updates.md
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily Dependency Updater workflow to your repository
14-
gh aw add githubnext/agentics/daily-dependency-updates --pr
14+
gh aw add githubnext/agentics/daily-dependency-updates
1515
```
1616

17-
This creates a pull request to add the workflow to your repository. After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
17+
This walks you through adding the workflow to your repository. After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
1818

1919
```bash
2020
gh aw run daily-dependency-updates

docs/daily-perf-improver.md

Lines changed: 4 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -11,47 +11,29 @@ The [daily performance improver workflow](../workflows/daily-perf-improver.md?pl
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily Performance Improver workflow to your repository
14-
gh aw add githubnext/agentics/daily-perf-improver --pr
14+
gh aw add githubnext/agentics/daily-perf-improver
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
17+
This walks you through adding the workflow to your repository and running the workflow for the first time.
1818

19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
19+
You can start a run of this workflow immediately by running:
2220

2321
```bash
2422
gh aw run daily-perf-improver
2523
```
2624

27-
To run continuously (at most one instance running at a time and sending a trigger every 3 minutes), use:
25+
To run repeatedly (at most one instance running at a time and sending a trigger every 3 minutes), use:
2826

2927
```bash
3028
gh aw run daily-perf-improver --repeat 180
3129
```
3230

33-
❗IMPORTANT: GitHub Actions runs will **not** trigger on commits pushed by this workflow and will **not** tell you that CI has not been run unless you have enabled a specific custom check for this condition. **You must open/close the PR or hit "Update branch" if offered to trigger CI.Yes it's painful and yes it's just something you need to be aware of.
34-
3531
**Mandatory Checklist**
3632

3733
* [ ] I understand that, by default, the agentic portion of this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
3834

39-
* [ ] I have read the notes on coding tasks in the [main README](../README.md) and understand the implications.
40-
41-
* [ ] I am a repository admin or have sufficient permissions, and am happy for the safe-outputs portion of this workflow to push new branches to the repository.
42-
43-
* [ ] I have enabled "Allow GitHub Actions to create and approve pull requests" in the repository settings under "Actions > General"
44-
45-
* [ ] I have considered enabling "Always suggest updating pull request branches" in the repository settings
46-
47-
* [ ] If in a fork, I have enabled "GitHub Actions" and "GitHub Issues" in the fork repository settings
48-
4935
* [ ] I will review all pull requests very carefully, and carefully monitor the repository.
5036

51-
* [ ] I will operate this demonstrator for a time-limited period only (the default is 48h).
52-
53-
* [ ] I understand that GitHub Actions runs will **not** trigger on pull requests created by this workflow, see above.
54-
5537
## Configuration
5638

5739
1. The first run of the workflow will produce a pull request with inferred action pre-steps that need approval

docs/daily-plan.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,10 @@ The [daily plan workflow](../workflows/daily-plan.md?plain=1) will run daily to
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily Plan workflow to your repository
14-
gh aw add githubnext/agentics/daily-plan --pr
14+
gh aw add githubnext/agentics/daily-plan
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
18-
19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
22-
23-
```bash
24-
gh aw run daily-plan
25-
```
17+
This walks you through adding the workflow to your repository and running the workflow for the first time.
2618

2719
**Mandatory Checklist**
2820

docs/daily-progress.md

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -11,33 +11,21 @@ The [daily progress workflow](../workflows/daily-progress.md?plain=1) is an auto
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily Progress workflow to your repository
14-
gh aw add githubnext/agentics/daily-progress --pr
14+
gh aw add githubnext/agentics/daily-progress
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
17+
This walks you through adding the workflow to your repository.
1818

19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
19+
You can start a run of this workflow immediately by running:
2220

2321
```bash
2422
gh aw run daily-progress
2523
```
2624

2725
**Mandatory Checklist**
2826

29-
* [ ] I have read the notes on coding tasks in the [main README](../README.md) and understand the implications.
30-
3127
* [ ] I understand that this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
3228

33-
* [ ] I am a repository admin or have sufficient permissions, and am happy for this workflow to create issues, pull requests, and push new branches to the repository.
34-
35-
* [ ] I have enabled "Allow GitHub Actions to create and approve pull requests" in the repository settings under "Actions > General"
36-
37-
* [ ] I have considered enabling "Always suggest updating pull request branches" in the repository settings
38-
39-
* [ ] If in a fork, I have enabled "GitHub Actions" and "GitHub Issues" in the fork repository settings
40-
4129
* [ ] I will review all pull requests and issues created by this workflow very carefully, and carefully monitor the repository.
4230

4331
## Configuration

docs/daily-qa.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,12 @@ The [daily Adhoc QA workflow](../workflows/daily-qa.md?plain=1) will perform adh
1111
gh extension install github/gh-aw
1212

1313
# Add the Daily QA workflow to your repository
14-
gh aw add githubnext/agentics/daily-qa --pr
14+
gh aw add githubnext/agentics/daily-qa
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
17+
This walks you through adding the workflow to your repository.
1818

19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
19+
You can start a run of this workflow immediately by running:
2220

2321
```bash
2422
gh aw run daily-qa
Lines changed: 8 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,30 @@
1-
# 👥 Daily Team Status
1+
# 👥 Daily Repo Status
22

33
> For an overview of all available workflows, see the [main README](../README.md).
44
5-
The [daily team status workflow](../workflows/daily-team-status.md?plain=1) will assess activity in the repository and create a status report issue. You can edit the workflow to adjust the topics and texture of the report.
5+
The [daily repo status workflow](../workflows/daily-repo-status.md?plain=1) will assess activity in the repository and create a status report issue. You can edit the workflow to adjust the topics and texture of the report.
66

77
## Installation
88

99
```bash
1010
# Install the 'gh aw' extension
1111
gh extension install github/gh-aw
1212

13-
# Add the Daily Team Status workflow to your repository
14-
gh aw add githubnext/agentics/daily-team-status --pr
13+
# Add the Daily Repo Status workflow to your repository
14+
gh aw add githubnext/agentics/daily-repo-status
1515
```
1616

17-
This creates a pull request to add the workflow to your repository.
17+
This walks you through adding the workflow to your repository.
1818

19-
You must also add [choose a coding agent](https://github.github.com/gh-aw/reference/engines/) and add an API key secret for the agent to your repository.
20-
21-
After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
19+
You can start a run of this workflow immediately by running:
2220

2321
```bash
24-
gh aw run daily-team-status
22+
gh aw run daily-repo-status
2523
```
2624

27-
**Mandatory Checklist**
28-
29-
* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
30-
3125
## Configuration
3226

33-
This workflow requires no configuration and works out of the box. You can use local configuration to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/daily-team-status.config.md`.
34-
35-
2. Add MCPs to integrate with project management tools
27+
This workflow requires no configuration and works out of the box. You can use edit the workflow to customize triage criteria, labeling logic, customize issue categorization, modify automated responses.
3628

3729
## What it reads from GitHub
3830

0 commit comments

Comments
 (0)