chore: retrigger CI deploy-test after runner disk cleanup #131
No reviewers
Labels
No labels
architecture
backend
bug
ci
config
database
docker
documentation
duplicate
enhancement
frontend
help wanted
invalid
issue-25
issue-26
issue-42
issue-65
issue-67
issue-82
migrations
p0-critical
p1-high
p2-medium
p3-low
performance
quality
question
security
state-management
testing
timezone
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fastie81/honbu-manager!131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/retrigger-test"
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?
Trivial no-op (blank .gitignore entry) used to re-trigger the CI pipeline on main after the runner disk was cleaned up. deploy-test failed last run on 'no space left on device' during job-container pull; this merge fires the full pipeline (test -> lint -> build -> deploy-test) against the freed-space runner so we can confirm the test-node deployment completes.