akinus/akclip
1
0
Fork 0
Code Issues Pull requests Projects Releases 133 Packages Wiki Activity Actions

devops -> main #63

Merged
akinus merged 4 commits from devops into main 2026-06-28 04:27:51 +00:00
Conversation 0 Commits 4 Files changed 5 +251 -41
forgejo-actions commented 2026-06-28 04:26:53 +00:00
Copy link

Automated PR from CI pipeline.

Automated PR from CI pipeline.
Merge pull request 'issue-59 -> devops' (#62) from issue-59 into devops
Some checks failed
Level 2 — Devops / build-iterate (push) Failing after 4m4s
Details
Level 2 — Devops / create-pr (push) Has been skipped
Details
Level 2 — Devops / close-merged-issue (push) Has been skipped
Details
f3e5daa9fc 
Reviewed-on: #62
fix(ci): job succeeds when AI-fix loop recovers the build
All checks were successful
Level 2 — Devops / build-iterate (push) Successful in 1m50s
Details
Level 2 — Devops / create-pr (push) Successful in 9s
Details
Level 2 — Devops / close-merged-issue (push) Successful in 9s
Details
2ff5faae12 
When 'Build + Test (iteration 0)' failed and the AI-fix loop fixed the
build, the job was still reported as failed because the build step's
exit code propagated to the job. The AI-fix loop was running with
'if: failure()' but the job status was set by the first failed step.

Add 'continue-on-error: true' to the build step so it doesn't fail the
job on its own. The job now reports success when:
- The build passes on the first try (no fix needed), OR
- The AI-fix loop's retry produces a green build.

Change the AI-fix loop gate from 'if: failure()' to
'if: steps.build.outcome == failure' so it still triggers when the build
step itself failed (continue-on-error preserves the 'failure' outcome).

Without this, a build that requires an AI fix appears red in the Forgejo
UI even though opencode recovered the build - masking real problems
and forcing manual PR opens.
akinus merged commit cb6de692d1 into main 2026-06-28 04:27:51 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
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
akinus/akclip!63
No description provided.