s1d3sw1ped/grok-bot-bin
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 8 Wiki Activity

ci: Make update.yml open a PR when master push is blocked #14

New Issue
Closed
opened 2026-09-04 09:56:51 -05:00 by eva · 0 comments
eva commented 2026-09-04 09:56:51 -05:00
Owner
Copy Link
Copy Source

Problem

Nightly update.yml (schedule 17 6 * * *) detected Cursor Grok Bot 0.39.0, rewrote PKGBUILD, committed, then failed to push to protected master:

pre-receive hook declined / Internal Server Error on both HEAD→master and tag v0.39.0.

Run: https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/actions/runs/1437

Eva landed the bump manually as PR #13 → tag/release v0.39.0 (build green, package asset attached).

Ask

Change stay-current so the next bump does not need a human:

  • Prefer: workflow opens a PR (or pushes a chore/bump-* branch + opens PR) instead of pushing protected master/tags directly.
  • After merge, tag from CI or a follow-up job so build.yml still attaches the .pkg.tar.zst.
  • Keep failing loudly if the PR/tag path cannot land.

Do not weaken branch protection to make the old push work.

## Problem Nightly `update.yml` (schedule `17 6 * * *`) detected Cursor Grok Bot **0.39.0**, rewrote PKGBUILD, committed, then **failed to push** to protected `master`: `pre-receive hook declined` / Internal Server Error on both `HEAD→master` and tag `v0.39.0`. Run: https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/actions/runs/1437 Eva landed the bump manually as PR https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/pulls/13 → tag/release `v0.39.0` (build green, package asset attached). ## Ask Change stay-current so the next bump does not need a human: - Prefer: workflow opens a PR (or pushes a `chore/bump-*` branch + opens PR) instead of pushing protected `master`/tags directly. - After merge, tag from CI or a follow-up job so `build.yml` still attaches the `.pkg.tar.zst`. - Keep failing loudly if the PR/tag path cannot land. Do not weaken branch protection to make the old push work.
ash was assigned by eva 2026-09-04 09:56:51 -05:00
linus closed this issue 2026-09-04 11:10:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ash blake eva linus moss pike s1d3sw1ped
No Assignees ash
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/grok-bot-bin#14
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?