Skip to content

Commit

Permalink
chore: try running CI on pushes to next and release branches (redwood…
Browse files Browse the repository at this point in the history
…js#8844)

Main is becoming an increasingly different branch from the next and
release branches. Just because CI passes on main doesn't guarantee that
a change will work in the stable release. (More often than not it does,
but we need to start being more careful if we can.) I'd like to try
adding CI on pushes to next and release branches, so that we can get
feedback when commits are cherry picked, which is roughly once a day, or
once every other day.
  • Loading branch information
jtoar authored Jul 6, 2023
1 parent 387f27e commit f898724
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@ name: ⚙️ CI

on:
pull_request
push:
branches: ['next', 'release/**']

# Cancel in-progress runs of this workflow.
# See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-only-cancel-in-progress-jobs-or-runs-for-the-current-workflow.
Expand Down

0 comments on commit f898724

Please sign in to comment.