Skip to content

Conversation

@jumski
Copy link
Contributor

@jumski jumski commented Nov 17, 2025

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Nov 17, 2025

⚠️ No Changeset found

Latest commit: bb77685

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@graphite-app
Copy link
Contributor

graphite-app bot commented Nov 17, 2025

Merge activity

  • Nov 17, 10:42 AM UTC: jumski added this pull request to the Graphite merge queue.
  • Nov 17, 10:43 AM UTC: CI is running for this pull request on a draft pull request (#381) due to your merge queue CI optimization settings.
  • Nov 17, 10:44 AM UTC: Merged by the Graphite merge queue via draft PR: #381.

Copy link
Contributor Author

jumski commented Nov 17, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge:queue - adds this PR to the back of the merge queue
  • hotfix:queue - for urgent hot fixes, skip the queue and merge this PR next

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.

graphite-app bot pushed a commit that referenced this pull request Nov 17, 2025
@nx-cloud
Copy link

nx-cloud bot commented Nov 17, 2025

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

To disable these notifications, a workspace admin can disable them in workspace settings.


View your CI Pipeline Execution ↗ for commit bb77685

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

@graphite-app graphite-app bot closed this Nov 17, 2025
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a 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".

Comment on lines +5 to +7
push:
branches: [main]
# TODO: Optimize - separate deployment workflow to avoid re-running tests on main

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants