Skip to content

chore: update managed mounted tools - #47

Merged
github-actions[bot] merged 1 commit into
mainfrom
automated/update-managed-tools
Jul 6, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
automated/update-managed-tools

Conversation

@silverknightkma-s-app

Copy link
Copy Markdown
Contributor

Updates pinned managed mounted tool versions in managed-tools/manifest.json.

@github-actions
github-actions Bot merged commit 576d424 into main Jul 6, 2026
8 of 9 checks passed
@SilverKnightKMA
SilverKnightKMA deleted the automated/update-managed-tools branch July 12, 2026 04:27
SilverKnightKMA added a commit that referenced this pull request Jul 20, 2026
)

PR #64 misdiagnosed the lingering branch as a side effect of reusing a
fixed branch name. The real cause is a long-standing GitHub platform
bug (orgs/community#63409): when a PR is merged via a bot/App token
(actor: github-actions[bot]), the repo setting delete_branch_on_merge
is silently ignored. User-merged PRs on the same repo delete fine.

Evidence from this repo's timeline:
- PRs #44, #45, #47, #55, #62 (merged_by=github-actions[bot]): no
  auto-delete; branches lingered until manually removed.
- PRs #58, #59, #60 (merged_by=SilverKnightKMA): auto-deleted within
  1 second of merge.

Renaming the branch per run (PR #64) only stops branch reuse; it does
not delete the merged branch. Without this workflow, merged branches
would accumulate indefinitely one per week.

This workflow explicitly deletes the head branch on PR close (merged),
scoped to same-repo automation branches (automated/*, dependabot/*,
deps/*, chore/*) or trusted bot authors. Fork branches are skipped and
deletion is idempotent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant