fidget/Guksu-Motor
1
0
Fork 0
Code Issues 6 Pull requests Projects Releases 4 Packages Wiki Activity Actions

Retarget or remove Issue Status From Pull Requests automation #5

New issue
Open
opened 2026-08-05 08:36:55 -04:00 by fidget · 0 comments
fidget commented 2026-08-05 08:36:55 -04:00
Owner
Copy link

Problem

.github/workflows/issue-status-from-prs.yml cannot currently fire because it listens only for pull requests targeting a branch that does not exist in Guksu Motor:

on:
  pull_request_target:
    branches: [staging]

The live branches are main, testing, and honcho-fixes. There is no staging branch, and the current 37-run Actions history contains zero runs for this workflow.

Additional incompatibilities

Even after correcting the branch name, the job requests ubuntu-latest, while Guksu's active runner only advertises [self-hosted, linux, x64, nix].

The implementation and labels are also inherited around the old branch model:

  • in-pr: “Has an open pull request targeting staging”
  • fixed-in-staging: “Already fixed in staging…”
  • actions/github-script and GitHub REST client calls have not been validated against the live Forgejo API.

Proposed resolution

Decide whether Guksu wants this issue-state automation:

  1. Port it: retarget the workflow and label semantics to Guksu's real integration branch (testing, if that remains the intended branch), use the self-hosted runner, and validate all label/PR calls against Forgejo.
  2. Remove it: delete the dead workflow and any stale in-pr / fixed-in-staging labels or documentation.

Do not simply rename staging to testing without reviewing the close/merge semantics. The workflow currently distinguishes “merged into staging” from final closure after staging reaches main; Guksu's desired issue lifecycle should be explicit.

Acceptance criteria

  • The workflow listens to a live, intentionally chosen branch.
  • Job labels match the available Guksu runner.
  • Label names and descriptions match Guksu's actual branch lifecycle.
  • A test PR containing Closes #<issue> applies the open-PR label.
  • Editing, closing without merge, and merging reconcile labels correctly.
  • Multiple PRs referencing the same issue do not remove the active label prematurely.
  • A real Forgejo run reaches an explicit terminal success state.
## Problem `.github/workflows/issue-status-from-prs.yml` cannot currently fire because it listens only for pull requests targeting a branch that does not exist in Guksu Motor: ```yaml on: pull_request_target: branches: [staging] ``` The live branches are `main`, `testing`, and `honcho-fixes`. There is no `staging` branch, and the current 37-run Actions history contains zero runs for this workflow. ## Additional incompatibilities Even after correcting the branch name, the job requests `ubuntu-latest`, while Guksu's active runner only advertises `[self-hosted, linux, x64, nix]`. The implementation and labels are also inherited around the old branch model: - `in-pr`: “Has an open pull request targeting staging” - `fixed-in-staging`: “Already fixed in staging…” - `actions/github-script` and GitHub REST client calls have not been validated against the live Forgejo API. ## Proposed resolution Decide whether Guksu wants this issue-state automation: 1. **Port it:** retarget the workflow and label semantics to Guksu's real integration branch (`testing`, if that remains the intended branch), use the self-hosted runner, and validate all label/PR calls against Forgejo. 2. **Remove it:** delete the dead workflow and any stale `in-pr` / `fixed-in-staging` labels or documentation. Do not simply rename `staging` to `testing` without reviewing the close/merge semantics. The workflow currently distinguishes “merged into staging” from final closure after staging reaches `main`; Guksu's desired issue lifecycle should be explicit. ## Acceptance criteria - [ ] The workflow listens to a live, intentionally chosen branch. - [ ] Job labels match the available Guksu runner. - [ ] Label names and descriptions match Guksu's actual branch lifecycle. - [ ] A test PR containing `Closes #<issue>` applies the open-PR label. - [ ] Editing, closing without merge, and merging reconcile labels correctly. - [ ] Multiple PRs referencing the same issue do not remove the active label prematurely. - [ ] A real Forgejo run reaches an explicit terminal success state.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
testing
honcho-fixes
v2.4.4a
v2.3.5c
v2.3.5b
v2.3.5a
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fidget/Guksu-Motor#5
No description provided.