-
Notifications
You must be signed in to change notification settings - Fork 14
ci: run workflow on main branch pushes #380
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Merge activity
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx affected -t lint typecheck test --parallel -... |
❌ Failed | 7m 5s | View ↗ |
nx affected -t test:e2e --parallel --base=origi... |
✅ Succeeded | 5m 21s | View ↗ |
☁️ Nx Cloud last updated this comment at 2025-11-17 10:51:09 UTC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| push: | ||
| branches: [main] | ||
| # TODO: Optimize - separate deployment workflow to avoid re-running tests on main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Push to main triggers skip all work
The new push trigger for main means this workflow now runs on merges, but NX_BASE is still set to origin/main while NX_HEAD is HEAD. On a push event those refs are identical, so every nx affected invocation reports no affected projects and the build/test/deploy jobs effectively do nothing. As a result, pushes to main won’t rebuild or deploy the website even though the workflow runs.
Useful? React with 👍 / 👎.

No description provided.