Skip to content

nested-worktree-prune classifies a live session's work_dir as safely prunable: gc doctor --fix force-removes a running refinery's worktree (gc-9hy4l) #224

nested-worktree-prune classifies a live session's work_dir as safely prunable: gc doctor --fix force-removes a running refinery's worktree (gc-9hy4l)

nested-worktree-prune classifies a live session's work_dir as safely prunable: gc doctor --fix force-removes a running refinery's worktree (gc-9hy4l) #224

Workflow file for this run

name: Auto-label new issues and PRs
on:
issues:
types: [opened, reopened]
pull_request_target:
types: [opened, reopened, ready_for_review]
permissions: {}
jobs:
# pull_request_target is safe here because this job never checks out or runs
# pull request code; it only labels the issue/PR from event metadata.
add-triage-label:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- name: Add needs-triage label
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8
with:
script: |
const pullRequest = context.payload.pull_request;
if (pullRequest?.draft) {
console.log(`Skipping draft PR #${pullRequest.number}`);
return;
}
const number = context.issue?.number || pullRequest?.number;
if (!number) {
core.setFailed('Unable to determine issue or PR number');
return;
}
await github.rest.issues.addLabels({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: number,
labels: ['status/needs-triage']
});