Skip to content

chore(.github): drop self fr-gate caller on main (promote #86) - #87

Merged
LukasWodka merged 3 commits into
mainfrom
develop
Jul 26, 2026
Merged

chore(.github): drop self fr-gate caller on main (promote #86)#87
LukasWodka merged 3 commits into
mainfrom
develop

Conversation

@LukasWodka

@LukasWodka LukasWodka commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Promotes the fr-gate-caller.yml removal from #86 up to main, and converges main/develop after the divergence heal.

After this, .github no longer runs its own FR-gate on promotions to its main (it has no deployable environment to functional-review on — RFC-0008 docs-treatment). The reusable fr-gate.yml that every other repo calls is untouched.

Net content diff = the single fr-gate-caller.yml deletion.

Part of #1273 / RFC-0008.


Note

Low Risk
CI-only change removing a workflow file; no application, auth, or data paths affected.

Overview
Removes the per-repo workflow fr-gate-caller.yml that invoked the reusable tracebloc/.github FR-gate on pull requests targeting staging, main, or master.

This repo will no longer run its own functional-review gate on promotions to main/staging (aligned with RFC-0008: no deployable environment here). The shared reusable workflow fr-gate.yml is unchanged and remains available for other repositories that still call it.

Reviewed by Cursor Bugbot for commit 408c33e. Bugbot is set up for automated code reviews on this repo. Configure here.

…d (D5) (#84)

D5 replaced the Priority single-select field with a binary 'priority' label.
This reusable still set the (now-removed) Priority field, so it would fail once
the field is deleted. Rewrite it to 'gh issue edit --add-label priority' — the
label is visible on the issue and filterable everywhere.

Prerequisite for deleting the Priority project field: this must be on main
first, or the workflow errors on the missing field.
chore(.github): heal develop divergence + drop self fr-gate caller
@LukasWodka

Copy link
Copy Markdown
Contributor Author

👋 Heads-up — Code review queue is at 39 / 30

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

@LukasWodka
LukasWodka merged commit 376a579 into main Jul 26, 2026
6 checks passed
LukasWodka added a commit that referenced this pull request Jul 28, 2026
A push routinely carries commits that already shipped further down the
pipeline: a staging->develop back-merge re-pushes Prod PRs to develop, and
a develop==main fast-forward does the same. advance-deploy-env blindly set
every PR in the push to the branch's column, un-shipping those cards (seen
live: .github #87/#88/#89/#92 stranded at On dev after yesterday's ff, #95
demoted from Prod today; engine#540's back-merge would demote its whole
staging history next). Now the per-PR query also reads the current Status
and the update is skipped unless the target rank is strictly higher.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to 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.

1 participant