ci(forgejo): port canola-branch automation workflows #344
No reviewers
Labels
No labels
autorelease: pending
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream/digest
upstream/pr
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/canola.nvim!344
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/forgejo-automation-workflows-canola"
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?
Summary
canolascripts/upstream_digest.pywithout the GitHub CLIcanolaupstream digest PRcanolaandci/upstream-digest-canolacurl,git,jq, andpython3tools to the dev shellBranch note
This PR targets
canola. It intentionally keepsworkflow_dispatchbut does not rely onschedule, because Forgejo ignores scheduled workflows on non-default branches. The scheduled canola digest is launched from themainworkflow PR, which checks outcanolaand opens PRs back tocanola.Verification
yqshfmt,shellcheck, andbash -npython3 -m py_compile scripts/upstream_digest.pynix develop .#ci --command just formatnix develop .#ci --command just lintci/upstream-digest-canolaand refused to push/open a PRquestionremoved and was closedcanolaPR #254, verified reviewer appeared, then canceled back to emptyKnown test issue
Local
just testcurrently fails on baselineorigin/canolatoo:spec/altbuf_spec.lua @ 56times out waiting forUser. This appears pre-existing/local-environment-sensitive, not caused by this workflow port, but it must be fixed in follow-up and is recorded in nixAGENTS.md.4eeb1b597c918159b1db