[PR #13] [MERGED] ci: open a PR from the nightly refresh instead of pushing to protected main #16

New issue

Closed

opened 2026-10-26 22:22:58 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 22:22:58 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/ComfyUI-Standalone-Environments/pull/13
Author: @Kosinkadink
Created: 7/28/2026
Status: ✅ Merged
Merged: 7/28/2026
Merged by: @Kosinkadink

Base: main ← Head: fix/nightly-refresh-pr-flow

📝 Commits (1)

d6399a7 ci: open a PR from the nightly refresh instead of pushing to protected main

📊 Changes

1 file changed (+27 additions, -6 deletions)

View changed files

📝 .github/workflows/refresh-nightly-stacks.yml (+27 -6)

📄 Description

The scheduled Refresh Nightly Torch Stacks run on 2026-07-27 failed at the "Commit updated manifest" step: branch protection on main now rejects direct pushes (GH006: Changes must be made through a pull request), so nightly manifest refreshes were effectively dead.

This changes the refresh workflow to commit to a rolling bot/refresh-nightly-stacks branch (force-pushed, since a newer resolve supersedes an older one) and open/reuse a PR against main instead of pushing directly.

The R2 upload is unchanged and still happens directly from the refreshed working tree in the same run, so nightly wheel-pin decay is handled without waiting for a human to merge; the PR only syncs main with what is already live on R2.

Known caveat (documented in the workflow): PRs created with GITHUB_TOKEN do not trigger pull_request CI. If required checks block the bot PR, close/reopen it to run them - the manifest was already validated by the refresh run itself.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/ComfyUI-Standalone-Environments/pull/13 **Author:** [@Kosinkadink](https://github.com/Kosinkadink) **Created:** 7/28/2026 **Status:** ✅ Merged **Merged:** 7/28/2026 **Merged by:** [@Kosinkadink](https://github.com/Kosinkadink) **Base:** `main` ← **Head:** `fix/nightly-refresh-pr-flow` --- ### 📝 Commits (1) - [`d6399a7`](https://github.com/Comfy-Org/ComfyUI-Standalone-Environments/commit/d6399a772369e9aa99f49f36651193326e7570d1) ci: open a PR from the nightly refresh instead of pushing to protected main ### 📊 Changes **1 file changed** (+27 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/refresh-nightly-stacks.yml` (+27 -6) </details> ### 📄 Description The scheduled `Refresh Nightly Torch Stacks` run on 2026-07-27 failed at the "Commit updated manifest" step: branch protection on `main` now rejects direct pushes (`GH006: Changes must be made through a pull request`), so nightly manifest refreshes were effectively dead. This changes the refresh workflow to commit to a rolling `bot/refresh-nightly-stacks` branch (force-pushed, since a newer resolve supersedes an older one) and open/reuse a PR against `main` instead of pushing directly. The R2 upload is unchanged and still happens directly from the refreshed working tree in the same run, so nightly wheel-pin decay is handled without waiting for a human to merge; the PR only syncs `main` with what is already live on R2. Known caveat (documented in the workflow): PRs created with `GITHUB_TOKEN` do not trigger `pull_request` CI. If required checks block the bot PR, close/reopen it to run them - the manifest was already validated by the refresh run itself. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-26 22:22:58 +00:00