Skip to content

Comments

feat: restrict-template-expressions: move type to labeled range#724

Merged
graphite-app[bot] merged 1 commit intomainfrom
02-21-feat_restrict-template-expressions_move_type_to_labeled_range
Feb 22, 2026
Merged

feat: restrict-template-expressions: move type to labeled range#724
graphite-app[bot] merged 1 commit intomainfrom
02-21-feat_restrict-template-expressions_move_type_to_labeled_range

Conversation

@camchenry
Copy link
Member

@camchenry camchenry commented Feb 22, 2026

The current error message is very awkwardly worded, moving the type to a labeled range makes it read more clearly I think.

Copy link
Member Author

camchenry commented Feb 22, 2026


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.

@camc314 camc314 self-assigned this Feb 22, 2026
Copy link
Contributor

camc314 commented Feb 22, 2026

Merge activity

The current error message is very awkwardly worded, moving the type to a labeled range makes it read more clearly I think.
@graphite-app graphite-app bot force-pushed the 02-21-feat_restrict-template-expressions_move_type_to_labeled_range branch from bacafce to f3fe501 Compare February 22, 2026 13:47
@graphite-app graphite-app bot merged commit f3fe501 into main Feb 22, 2026
8 checks passed
@graphite-app graphite-app bot deleted the 02-21-feat_restrict-template-expressions_move_type_to_labeled_range branch February 22, 2026 13:53
@graphite-app graphite-app bot removed the 0-merge label Feb 22, 2026
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