Skip to content

Fill In the Release-Watch Timeout Placeholder #944

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ptr727 merged 1 commit into from
Aug 23, 2026
Merged

Fill In the Release-Watch Timeout Placeholder #944

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions .agents/skills/merge-and-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,12 +93,14 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
distinctly, the ref changed mid-dispatch, rather than folding it into an ordinary absent-run
timeout. Report and stop rather than guessing once the interval elapses with zero or more than
one candidate still matching. Only once exactly one candidate is confirmed, poll that one run
id to completion in
one further bounded background wait with an explicit timeout, `timeout <seconds> gh run
watch <run-id> --repo owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent
bounded-wait mechanism on a host without it (macOS without coreutils, native Windows), and
report a timeout separately from a completed run's own conclusion, the tag or version it
produced. A run that fails, times out, or never starts is reported, never silently retried.
id to completion in one further bounded background wait with an explicit, finite timeout,
2700 seconds (45 minutes, matching `scripts/pr_review.py`'s own default) unless the maintainer
states a different bound for this specific release: `timeout 2700 gh run watch <run-id> --repo
owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent bounded-wait
mechanism enforcing the same bound on a host without it (macOS without coreutils, native
Windows). Report a timeout separately from a completed run's own conclusion, the tag or
version it produced. A run that fails, times out, or never starts is reported, never silently
retried.
7. In the hub, when the chosen scope includes a release, bring this checkout to the merged
content without discarding or mixing in anything local. First assert `git status --porcelain
--untracked-files=all --ignored` is empty, and stop and report rather than proceeding over any
Expand Down
2 changes: 1 addition & 1 deletion .claude-plugin/fleet-skills/.source-digest
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1b7f99942fd01422
b8df12b7c8013f3d
14 changes: 8 additions & 6 deletions .claude-plugin/fleet-skills/skills/merge-and-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,12 +93,14 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
distinctly, the ref changed mid-dispatch, rather than folding it into an ordinary absent-run
timeout. Report and stop rather than guessing once the interval elapses with zero or more than
one candidate still matching. Only once exactly one candidate is confirmed, poll that one run
id to completion in
one further bounded background wait with an explicit timeout, `timeout <seconds> gh run
watch <run-id> --repo owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent
bounded-wait mechanism on a host without it (macOS without coreutils, native Windows), and
report a timeout separately from a completed run's own conclusion, the tag or version it
produced. A run that fails, times out, or never starts is reported, never silently retried.
id to completion in one further bounded background wait with an explicit, finite timeout,
2700 seconds (45 minutes, matching `scripts/pr_review.py`'s own default) unless the maintainer
states a different bound for this specific release: `timeout 2700 gh run watch <run-id> --repo
owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent bounded-wait
mechanism enforcing the same bound on a host without it (macOS without coreutils, native
Windows). Report a timeout separately from a completed run's own conclusion, the tag or
version it produced. A run that fails, times out, or never starts is reported, never silently
retried.
7. In the hub, when the chosen scope includes a release, bring this checkout to the merged
content without discarding or mixing in anything local. First assert `git status --porcelain
--untracked-files=all --ignored` is empty, and stop and report rather than proceeding over any
Expand Down
14 changes: 8 additions & 6 deletions .github/skills/merge-and-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,12 +93,14 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
distinctly, the ref changed mid-dispatch, rather than folding it into an ordinary absent-run
timeout. Report and stop rather than guessing once the interval elapses with zero or more than
one candidate still matching. Only once exactly one candidate is confirmed, poll that one run
id to completion in
one further bounded background wait with an explicit timeout, `timeout <seconds> gh run
watch <run-id> --repo owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent
bounded-wait mechanism on a host without it (macOS without coreutils, native Windows), and
report a timeout separately from a completed run's own conclusion, the tag or version it
produced. A run that fails, times out, or never starts is reported, never silently retried.
id to completion in one further bounded background wait with an explicit, finite timeout,
2700 seconds (45 minutes, matching `scripts/pr_review.py`'s own default) unless the maintainer
states a different bound for this specific release: `timeout 2700 gh run watch <run-id> --repo
Comment on lines +97 to +98

@qodo-code-review qodo-code-review Bot Aug 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Capitalize bind word correctly 📘 Rule violation ⚙ Maintainability

The PR title uses In in the middle of the title, but in is a designated lowercase bind word when
it is not first or last. Rename it to Fill in the Release-Watch Timeout Placeholder.
Agent Prompt 
## Issue description
The PR title `Fill In the Release-Watch Timeout Placeholder` violates the title-case rule because `In` is a middle-position bind word that must be lowercase.

## Issue Context
The required title form is `Fill in the Release-Watch Timeout Placeholder`; the title otherwise remains imperative and within the character limit.

## Fix Focus Areas
- .github/skills/merge-and-release/SKILL.md[97-98]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

owner/repo --exit-status` on a host with GNU `timeout`, or the equivalent bounded-wait
mechanism enforcing the same bound on a host without it (macOS without coreutils, native
Windows). Report a timeout separately from a completed run's own conclusion, the tag or
version it produced. A run that fails, times out, or never starts is reported, never silently
retried.
7. In the hub, when the chosen scope includes a release, bring this checkout to the merged
content without discarding or mixing in anything local. First assert `git status --porcelain
--untracked-files=all --ignored` is empty, and stop and report rather than proceeding over any
Expand Down