<@U090ER7JPHA> open a PR that adds the github work...
# slackbot-chatter
l
@nutritious-balloon-65098 open a PR that adds the github workflow that auto-comments and closes stale issues and PRs from the OpenHands/OpenHands repo to the OpenHands/software-agent-sdk repo.
n
I'm on it! Graham Neubig can track my progress here.
Summary The stale issues/PRs workflow already exists in the
OpenHands/software-agent-sdk
repository at
.github/workflows/stale.yml
. Comparison of the two workflows: | Feature | OpenHands/OpenHands | software-agent-sdk | | - | - | - | | Action version |
actions/stale@v9
|
actions/stale@v10
(newer) | | Days before stale | 40 | 40 | | Days before close | 10 | 10 | | Exempt labels |
roadmap,backlog,app-team
|
roadmap,backlog
| | Operations per run | 300 | 150 | | Fork check | No | Yes ✓ | Key observations: • The software-agent-sdk version is actually more up-to-date (using v10 instead of v9) • It includes a fork check (
if: github.repository == 'OpenHands/software-agent-sdk'
) which is a good practice to prevent scheduled jobs from running in forks • The only missing element is the
app-team
exempt label, which may not be relevant for the agent-sdk repo No PR is needed since the workflow already exists with equivalent (and in some ways better) configuration. <sub>View full conversation</sub>
l
@nutritious-balloon-65098 Ah, I see why this isn’t activating. We have a separate github workflow that asks the agent to comment on stale PRs. In the prompt there write “DO NOT comment if you have already commented once and there has not yet been a reply.”
n
I'm on it! Graham Neubig can continue tracking my progress here.
Summary I investigated both repositories and found that the stale issues/PRs workflow already exists in the software-agent-sdk repo. Comparison of the two workflows: | Feature | OpenHands/OpenHands | OpenHands/software-agent-sdk | | - | - | - | | File |
.github/workflows/stale.yml
|
.github/workflows/stale.yml
| | Action version |
actions/stale@v9
|
actions/stale@v10
(newer) | | Days before stale | 40 | 40 | | Days before close | 10 | 10 | | Exempt labels |
roadmap,backlog,app-team
|
roadmap,backlog
| | Operations per run | 300 | 150 | | Fork check | No | Yes (
if: github.repository == 'OpenHands/software-agent-sdk'
) | The software-agent-sdk version is actually slightly more up-to-date (using v10 instead of v9) and includes a fork check which is a good practice. Regarding the agent-based stale PR commenting workflow You mentioned a separate workflow that "asks the agent to comment on stale PRs" with a prompt containing "DO NOT comment if you have already commented once and there has not yet been a reply." I searched both repositories but could not find this workflow in either: • OpenHands/OpenHands • OpenHands/software-agent-sdk Could you clarify: 1. Which repository contains this agent-based stale PR workflow? 2. Or would you like me to create a new workflow with this functionality? No PR was created since the basic stale workflow already exists in software-agent-sdk. <sub>View full conversation</sub>
Summary I've created a draft PR to add the duplicate comment prevention instruction to the
assign-reviews.yml
workflow in the software-agent-sdk repo. PR Created: https://github.com/OpenHands/software-agent-sdk/pull/1516 Changes Made Added the following instruction to the
PROMPT_STRING
in `.github/workflows/assign-reviews.yml`:
Copy code
IMPORTANT: DO NOT comment if you have already commented once and there has not yet been a reply.
Before posting any "[Automatic Post]" comment, check the issue/PR comments to see if there is
already an "[Automatic Post]" comment from this workflow. If there is, and no one has replied
to it yet, skip that issue/PR entirely.
Checklist • ✅ Added the "DO NOT comment if you have already commented once and there has not yet been a reply" instruction • ✅ Instruction placed prominently at the top of the prompt (after the general intro) • ✅ Changes are minimal and focused only on the requested modification • ✅ PR created as draft for review Note The software-agent-sdk repo already had a
stale.yml
workflow (using
actions/stale@v10
) that handles basic stale issue/PR marking and closing. The
assign-reviews.yml
workflow is the agent-based workflow that posts "[Automatic Post]" comments, which is what needed the duplicate comment prevention. <sub>View full conversation</sub>