Repository navigation
sync: close spin's issue while nothing is behind, reopen it when something is - #63
Merged
Merged
Conversation
…eopened when something is "Site vs spin main" was a dashboard kept open for ever. It now says what keeps it open - the site not on spin's newest release, a spin-machine pin short of the newest, a release with no image, a chain workflow whose last run did not succeed - and is closed when nothing does, the same issue reopened when something does again. What spin main has past the pin and what spinbox.dev runs are reported and keep nothing open: main is past every release between two of them, and spinbox.dev is reinstalled when its owner decides. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
spin#657 ("Site vs spin main") was kept open for ever. Now:
machine.yml,propose.yml,fresh-install.yml) whose last run did not succeed, never ran or could not be read. A run still in progress counts as nothing yet.completed). Something behind: the same issue is reopened - found among the bot's issues in any state, newest first - and opened only if there was never one.Dry run today (
-print): images.json (v20261026.01's AMI is building) andfresh-install.yml, whose last run on 2026-10-25 failed.Tests:
TestTheIssueIsClosedWhileSettledAndTheSameOneReopened(seen red with closing planted out), and the chain test now holds which links are behind.🤖 Generated with Claude Code