Skip to content
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

Allow for under development feature flags #3119

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

vinistock
Copy link
Member

@vinistock vinistock commented Jan 31, 2025

Motivation

In addition to being able to roll out feature flags gradually, it would be nice if we could have flags that are only on if explicitly enabled. That allows us to hide under development functionality that's not ready even for beta testers.

This PR adds support for under development flags.

Implementation

Started considering -1 as the indication that a flag is under development. If the value is -1, that flag is not enabled based on the all setting and can only be turned on by explicitly opting in.

Automated Tests

Added a test.

Copy link
Member Author

vinistock commented Jan 31, 2025


How to use the Graphite Merge Queue

Add the label graphite-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.

@vinistock vinistock self-assigned this Jan 31, 2025
@vinistock vinistock added vscode This pull request should be included in the VS Code extension's release notes enhancement New feature or request labels Jan 31, 2025 — with Graphite App
@vinistock vinistock requested review from andyw8 and st0012 January 31, 2025 16:47
@vinistock vinistock marked this pull request as ready for review January 31, 2025 16:49
@vinistock vinistock requested a review from a team as a code owner January 31, 2025 16:49
@vinistock vinistock force-pushed the 01-31-allow_for_under_development_feature_flags branch from c2ba939 to baabe7d Compare January 31, 2025 20:34
@vinistock vinistock added the graphite-merge Ship this PR using Graphite's merge queue label Feb 3, 2025
Copy link
Member Author

vinistock commented Feb 3, 2025

Merge activity

  • Feb 3, 8:51 AM EST: The merge label 'graphite-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Feb 3, 8:53 AM EST: A user added this pull request to the Graphite merge queue.
  • Feb 3, 9:18 AM EST: A user merged this pull request with the Graphite merge queue.

### Motivation

In addition to being able to roll out feature flags gradually, it would be nice if we could have flags that are only on if explicitly enabled. That allows us to hide under development functionality that's not ready even for beta testers.

This PR adds support for under development flags.

### Implementation

Started considering -1 as the indication that a flag is under development. If the value is -1, that flag is not enabled based on the `all` setting and can only be turned on by explicitly opting in.

### Automated Tests

Added a test.
@graphite-app graphite-app bot force-pushed the 01-31-allow_for_under_development_feature_flags branch from baabe7d to 76294b3 Compare February 3, 2025 13:53
@graphite-app graphite-app bot merged commit 76294b3 into main Feb 3, 2025
42 checks passed
@graphite-app graphite-app bot deleted the 01-31-allow_for_under_development_feature_flags branch February 3, 2025 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request graphite-merge Ship this PR using Graphite's merge queue vscode This pull request should be included in the VS Code extension's release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants