Skip to content

Conversation

@Dunqing
Copy link
Member

@Dunqing Dunqing commented Sep 16, 2025

Distinguish formatter coverage errors and show parse errors, which help us quickly identify problems.

@github-actions github-actions bot added the C-enhancement Category - New feature or request label Sep 16, 2025
Copy link
Member Author

Dunqing commented Sep 16, 2025


How to use the Graphite Merge Queue

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

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - 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.

@Dunqing Dunqing force-pushed the 09-16-feat_tasks_coverage_shows_parse_errors_and_mismatch_information_for_the_formatter branch 2 times, most recently from 11cbbce to 6d7f209 Compare September 17, 2025 05:12
@Dunqing Dunqing marked this pull request as ready for review September 17, 2025 05:26
Copilot AI review requested due to automatic review settings September 17, 2025 05:26
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.


Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@graphite-app graphite-app bot added the 0-merge Merge with Graphite Merge Queue label Sep 17, 2025
@graphite-app
Copy link
Contributor

graphite-app bot commented Sep 17, 2025

Merge activity

  • Sep 17, 6:02 AM UTC: leaysgur added this pull request to the Graphite merge queue.
  • Sep 17, 6:07 AM UTC: The Graphite merge queue couldn't merge this PR because it was not satisfying all requirements (Failed CI: 'Test Linux', 'autofix', 'Test wasm32-wasip1-threads', 'Test NAPI', 'Lint', 'Conformance', 'Minification Size', 'AST Changes', 'Allocations', 'Linter changes').
  • Sep 17, 6:29 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Sep 17, 9:29 AM UTC: Boshen added this pull request to the Graphite merge queue.
  • Sep 17, 9:34 AM UTC: Merged by the Graphite merge queue.

graphite-app bot pushed a commit that referenced this pull request Sep 17, 2025
… the formatter (#13812)

Distinguish formatter coverage errors and show parse errors, which help us quickly identify problems.
@graphite-app graphite-app bot force-pushed the 09-16-feat_tasks_coverage_shows_parse_errors_and_mismatch_information_for_the_formatter branch from 6d7f209 to 54ad378 Compare September 17, 2025 06:03
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Sep 17, 2025
@leaysgur leaysgur added the 0-merge Merge with Graphite Merge Queue label Sep 17, 2025
@leaysgur leaysgur self-assigned this Sep 17, 2025
… the formatter (#13812)

Distinguish formatter coverage errors and show parse errors, which help us quickly identify problems.
@graphite-app graphite-app bot force-pushed the 09-16-feat_tasks_coverage_shows_parse_errors_and_mismatch_information_for_the_formatter branch from bb3e0c9 to bf3cf39 Compare September 17, 2025 09:29
@graphite-app graphite-app bot merged commit bf3cf39 into main Sep 17, 2025
17 checks passed
@graphite-app graphite-app bot deleted the 09-16-feat_tasks_coverage_shows_parse_errors_and_mismatch_information_for_the_formatter branch September 17, 2025 09:34
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C-enhancement Category - New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants