You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"changeset status --since=main" does not cause CI Failure as per docs #2143
what is the checkout step's arguments? actions/checkout by default only fetches the latest commit with no git history unless you pass it fetch-depth: 0
fetch-depth: 0 was passed to the checkout. Below is the full action.
As you can see from the output of the run changeset correctly identified that no changeset exists, but does not return a failure code.
Activity
beeequeue commentedon Jul 2, 2026
what is the checkout step's arguments?
actions/checkoutby default only fetches the latest commit with no git history unless you pass itfetch-depth: 0emmet-opinionx commentedon Jul 6, 2026
fetch-depth: 0 was passed to the checkout. Below is the full action.
As you can see from the output of the run changeset correctly identified that no changeset exists, but does not return a failure code.
beeequeue commentedon Jul 6, 2026
apparently
statusonly exits with 1 if no changesets are found and any packages are found to have been "changed" (#504)could that be the issue? is changesets detecting the changes if there are any?
emmet-opinionx commentedon Jul 7, 2026
Yes thats it. Thanks.
Ill add a PR to get the above docs updated to avoid future confusion.