Skip to content

Commit

Permalink
chore(ci): get ci running on next (#10432)
Browse files Browse the repository at this point in the history
Follow up to #10393. After that
PR, CI no longer runs on the next branch when commits are pushed up.
This is important to double check if triage or a merge conflict was
resolved properly
  • Loading branch information
jtoar committed Apr 8, 2024
1 parent 5c66dcb commit cc51ac9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/actions/detect-changes/detectChanges.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -224,7 +224,7 @@ async function main() {

// If there's no branch, we're not in a pull request.
if (!branch) {
core.setOutput('code', false)
core.setOutput('code', true)
core.setOutput('rsc', false)
core.setOutput('ssr', false)
return
Expand Down

0 comments on commit cc51ac9

Please sign in to comment.