这是indexloc提供的服务，不要输入任何密码
Skip to content

feat: add options schema for no-misused-promises #399

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 11, 2025
Merged

feat: add options schema for no-misused-promises #399

merged 1 commit into from
Nov 11, 2025
+265 −116

Conversation

@camchenry
Copy link
Member

@camchenry camchenry commented Nov 11, 2025

No description provided.

@camchenry camchenry mentioned this pull request Nov 11, 2025
Merged
@camchenry Graphite App
Copy link
Member Author

camchenry commented Nov 11, 2025 •
edited
Loading

How to use the Graphite Merge Queue

Add the label 0-merge to this PR to add it to 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.

This was referenced Nov 11, 2025
Merged
Merged
Merged
@camchenry camchenry force-pushed the 11-11-feat_add_options_schema_for_no-misused-promises_ branch from 9eb0bde to ae85de5 Compare November 11, 2025 21:00
@camchenry camchenry marked this pull request as ready for review November 11, 2025 21:02
@camchenry camchenry changed the base branch from 11-11-feat_add_options_schema_for_no-meaningless-void-operator_ to graphite-base/399 November 11, 2025 21:21
@camchenry camchenry force-pushed the 11-11-feat_add_options_schema_for_no-misused-promises_ branch from ae85de5 to 1a46510 Compare November 11, 2025 21:21
@camchenry camchenry changed the base branch from graphite-base/399 to 11-11-feat_add_options_schema_for_no-meaningless-void-operator_ November 11, 2025 21:21
@camchenry Graphite App
Copy link
Member Author

camchenry commented Nov 11, 2025 •
edited by graphite-app bot
Loading

Merge activity

  • Nov 11, 9:21 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Nov 11, 9:40 PM UTC: camchenry added this pull request to the Graphite merge queue.
  • Nov 11, 10:01 PM UTC: The merge label '0-merge' was removed. This PR will no longer be merged by the Graphite merge queue
  • Nov 11, 10:01 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Nov 11, 10:01 PM UTC: graphite-app added this pull request to the Graphite merge queue.
  • Nov 11, 10:01 PM UTC: Merged by the Graphite merge queue.

This was referenced Nov 11, 2025
Merged
Merged
@graphite-app graphite-app bot force-pushed the 11-11-feat_add_options_schema_for_no-meaningless-void-operator_ branch from 52282e3 to cce934b Compare November 11, 2025 21:40
@graphite-app graphite-app bot force-pushed the 11-11-feat_add_options_schema_for_no-misused-promises_ branch from 1a46510 to 4fb0e00 Compare November 11, 2025 21:41
@graphite-app graphite-app bot removed the 0-merge label Nov 11, 2025
Base automatically changed from 11-11-feat_add_options_schema_for_no-meaningless-void-operator_ to main November 11, 2025 21:58
@graphite-app graphite-app bot added the 0-merge label Nov 11, 2025
@graphite-app graphite-app bot merged commit 4fb0e00 into main Nov 11, 2025
7 checks passed
@graphite-app graphite-app bot deleted the 11-11-feat_add_options_schema_for_no-misused-promises_ branch November 11, 2025 22:01
@graphite-app graphite-app bot removed the 0-merge label Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@camchenry