Skip to content

Commit 897b5c6

Browse files
committed
add repo assist
1 parent 6160ffc commit 897b5c6

1 file changed

Lines changed: 6 additions & 5 deletions

File tree

workflows/repo-assist.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,13 +39,14 @@ safe-outputs:
3939
labels: [automation, repo-assist]
4040
max: 3
4141
update-issue:
42-
target: "[Repo Assist]*"
42+
target: "*"
43+
#title-prefix: "[Repo Assist] "
4344
add-labels:
44-
allowed: [bug, enhancement, "help wanted", "good first issue"]
45+
allowed: [bug, enhancement, "help wanted", "good first issue", "spam", "off topic"]
4546
max: 3 # max labels (default: 3)
4647
target: "*" # "triggering" (default), "*", or number
4748
remove-labels:
48-
allowed: [bug, enhancement, "help wanted", "good first issue"]
49+
allowed: [bug, enhancement, "help wanted", "good first issue", "spam", "off topic"]
4950
max: 3 # max labels (default: 3)
5051
target: "*" # "triggering" (default), "*", or number
5152

@@ -125,7 +126,7 @@ Note: In issue comments and PR descriptions, identify yourself as "Repo Assist".
125126
- Restatements of what the issue author already said
126127
- Follow-ups to your own previous comments
127128
g. **AI Disclosure**: Begin every comment with a brief disclosure, e.g.:
128-
> 🤖 *This is an automated response from the repository's AI assistant.*
129+
> 🤖 *This is an automated response from RepoAssist, the repository's AI assistant.*
129130
3. Update your memory to note which issues you commented on. **If you commented on an issue, do not comment on it again in future runs** unless a human explicitly asks for follow-up.
130131

131132
### Task 2: Fix Issues via Pull Requests
@@ -305,7 +306,7 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
305306
306307
1. **Find or create the activity issue**:
307308
a. Search for an open issue with title prefix `[Repo Assist] Monthly Activity` and the label `repo-assist`.
308-
b. If one exists for the current month, update it. If it exists but is for a previous month, close it and create a new one for the current month.
309+
b. If one exists for the current month, update it using the `update_issue` MCP tool. If it exists but is for a previous month, close it and create a new one for the current month, linking to the previous one.
309310
c. If none exists, create a new issue.
310311
2. **Issue body format**: Update the issue body with a succinct activity log organized by date, plus a unified section of suggested actions for the maintainer. Use the following structure:
311312

0 commit comments

Comments
 (0)