Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork64
feat: fix duplicate CI workflow runs on pull requests#260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
CLAassistant commentedNov 5, 2025
|
Co-authored-by: hsluoyz <3787410+hsluoyz@users.noreply.github.com>
3c8c9d6 intomasterUh oh!
There was an error while loading.Please reload this page.
🎉 This PR is included in version 1.63.0 🎉 The release is available onGitHub release Yoursemantic-release bot 📦🚀 |
Uh oh!
There was an error while loading.Please reload this page.
GitHub Actions workflows were running twice on PRs: once for the
pushevent to the PR branch and once for thepull_requestevent, causing duplicate checks like "CI / macOS Latest (push)" and "CI / macOS Latest (pull_request)".Changes
Updated workflow triggers in 4 files to run on
pushonly for the master branch:.github/workflows/ci.yml.github/workflows/python_binding.yml.github/workflows/memcheck.yml.github/workflows/benchmark.ymlBefore:
After:
PRs now trigger workflows once via
pull_requestevent. Direct pushes to master still trigger viapushevent.Original prompt
✨ Let Copilot coding agentset things up for you — coding agent works faster and does higher quality work when set up for your repo.