Summary
The CI workflow currently runs on PRs targeting both develop and main. We want it to run only on PRs from develop → main, not on PRs into develop. This cuts noise and CI minutes on the day-to-day branch flow while keeping the gate where it actually matters (release into main).
Change
In .github/workflows/ci.yml, narrow the pull_request trigger from:
on:
pull_request:
branches: [develop, main]
workflow_dispatch:
to:
on:
pull_request:
branches: [main]
workflow_dispatch:
workflow_dispatch stays so the workflow can still be triggered manually on any branch when needed.
Verify
- Open a test PR into
develop → CI should NOT run.
- Open a test PR from
develop into main → CI SHOULD run.
- Trigger via the Actions UI on an arbitrary branch → still runs.
Affected files
loopstack/.github/workflows/ci.yml
Out of scope
release.yml and release-studio-docker.yml — not touched, those have their own triggers (tags / manual).
- Branch protection rules on
develop may currently require this CI check; if so, that requirement needs to be removed in the GitHub repo settings as part of this change.
Summary
The CI workflow currently runs on PRs targeting both
developandmain. We want it to run only on PRs fromdevelop→main, not on PRs intodevelop. This cuts noise and CI minutes on the day-to-day branch flow while keeping the gate where it actually matters (release intomain).Change
In
.github/workflows/ci.yml, narrow thepull_requesttrigger from:to:
workflow_dispatchstays so the workflow can still be triggered manually on any branch when needed.Verify
develop→ CI should NOT run.developintomain→ CI SHOULD run.Affected files
loopstack/.github/workflows/ci.ymlOut of scope
release.ymlandrelease-studio-docker.yml— not touched, those have their own triggers (tags / manual).developmay currently require this CI check; if so, that requirement needs to be removed in the GitHub repo settings as part of this change.