Skip to content

Promote develop to main After the Merge-Bot Caller Stub - #54

Merged
ptr727 merged 1 commit into
mainfrom
develop
Aug 16, 2026
Merged

Promote develop to main After the Merge-Bot Caller Stub#54
ptr727 merged 1 commit into
mainfrom
develop

Conversation

@ptr727

Copy link
Copy Markdown
Owner

Promote develop to main, carrying one change:

  • Adopt the Hub-Hosted Merge-Bot Caller Stub #53 Adopt the Hub-Hosted Merge-Bot Caller Stub: .github/workflows/merge-bot-pull-request.yml becomes the fleet caller stub reaching the hub's reusable merge-bot-task.yml at hub release 2.0.338, replacing the copied job bodies.

After this merges, main runs the stub too, so a Dependabot PR against main is the --merge half of the live proof, and the hub tracker (ptr727/ProjectTemplate docs/reusable-workflows.md "Rollout") ticks PhotoCleaner's stage-1 adoption, since main is this repo's ground-truth branch. No issue closes on this promotion.

The merge-bot's job bodies now live once in the hub as the reusable
merge-bot-task.yml, released at 2.0.338, and this repository is the
first to reach it rather than carry a copy. The stub keeps the
pull_request_target trigger, the per-PR concurrency group, and grants
GITHUB_TOKEN no scope, since every write in the task uses the App token.
No rules or delete-branch input is set: this repository runs no tracker
and keeps the hub's default behavior.
CopilotAI lite review requested due to automatic review settings August 16, 2026 02:40

CopilotAI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Promotes develop to main, carrying the repo’s adoption of the hub-hosted merge-bot reusable workflow so merge-bot behavior is driven by the shared ptr727/ProjectTemplate implementation rather than a copied local job definition.

Changes:

  • Replaces the local merge-bot workflow job bodies with a thin reusable-workflow caller stub.
  • Pins the called reusable workflow to hub release 2.0.338 (commit 20616e0a70613ad8727d567990f5d0e082f5275c), forwarding the two GitHub App secrets.
  • Sets workflow-level permissions: {} so the caller provides no GITHUB_TOKEN scope (the called workflow relies on the App token).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ptr727
ptr727 merged commit 4efcae8 into mainAug 16, 2026
16 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ptr727