ci: 🚀 track-downloads schedules auto-merge when checks are required #201
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
approved
area:client-host
area:item-interaction
area:meta-tooling
area:operator-dev-loop
area:repository-hygiene
area:typescript-sdk
area:website
blocked
bug
castra:bot-active
castra:human
change
checker:tobi
close-suggested
code
copilot-conflict
deferred
dependencies
docs-ok
enhancement
fast-track
groom:close-suggested
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human
human-required
intake
merge
merge-conflict
needs-scope
no-concept-doc
no-demo
plan-approved
plan-needs-revision
portfolio:infrastructure
portfolio:mixed
portfolio:product
portfolio:unknown
prioritize
prioritized
priority:high
priority:low
priority:medium
propose
ready
retro
retro-proposal
review
stage:backlog
stage:blocked
stage:code
stage:done
stage:intake
stage:merge
stage:propose
stage:review
stage:waiting
status:waiting
tracker
triage
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!201
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/201/head"
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?
What
Follow-up to #198. A live
workflow_dispatch(run #249) exposed a bug:goern/mainrequires Tekton status checks, so the workflow's immediate mergecurlreturns HTTP 405 while checks are pending →curl -fsSfails the job and leaves an orphaned bot PR open (this is what happened to #199).Fix
Merge step now:
merge_when_checks_succeed) so the snapshot PR lands unattended once checks pass and the job exits 0.Verification
This rework was validated live — the equivalent scheduled-merge call cleared #198 and #199 once their Tekton checks went green.
op1st Pipelines as Code/forgejo-mcp-code-scans-ctzfr is running.
Starting Pipelinerun forgejo-mcp-code-scans-ctzfr in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-ctzfr -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-nlhrz is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-nlhrz in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-nlhrz -fop1st Pipelines as Code/forgejo-mcp-code-scans-ctzfr has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-nlhrz has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check