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

fix: LEAP-40: Remove FF that is hard coded on feature-flag file #4704

Merged
merged 2 commits into from
Aug 29, 2023

Conversation

juliosgarbi
Copy link
Contributor

PR fulfills these requirements

  • Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
  • Tests for the changes have been added/updated (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
  • Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

  • Product design
  • Backend (Database)
  • Backend (API)
  • Frontend

Describe the reason for change

The FF_LSDV_E_297 is hard coded on the feature-flag file

What does this fix?

This fix removes the FF_LSDV_E_297 to be true from feature-flag file

What is the new behavior?

(if this is a breaking or feature change)

What is the current behavior?

(if this is a breaking or feature change)

What libraries were added/updated?

(list all with version changes)

Does this change affect performance?

(if so describe the impacts positive or negative)

Does this change affect security?

(if so describe the impacts positive or negative)

What alternative approaches were there?

(briefly list any if applicable)

What feature flags were used to cover this change?

(briefly list any if applicable)

Does this PR introduce a breaking change?

(check only one)

  • Yes, and covered entirely by feature flag(s)
  • Yes, and covered partially by feature flag(s)
  • No
  • Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

@netlify
Copy link

netlify bot commented Aug 28, 2023

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit ebfe4b4
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/64ecc8c08ffa4b000899528b

@netlify
Copy link

netlify bot commented Aug 28, 2023

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit ebfe4b4
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/64ecc8c054be2b0008130cab

@github-actions github-actions bot added the fix label Aug 28, 2023
@juliosgarbi juliosgarbi marked this pull request as draft August 29, 2023 11:18
@juliosgarbi juliosgarbi marked this pull request as ready for review August 29, 2023 11:21
@juliosgarbi juliosgarbi merged commit a4bab5d into develop Aug 29, 2023
27 checks passed
shayantabatabaee pushed a commit to shayantabatabaee/label-studio that referenced this pull request Sep 19, 2023
…nSignal#4704)

* fix: LEAP-40: Remove FF that is hard coded on feature-flag file

* ci: Build frontend

Workflow run: https://github.com/HumanSignal/label-studio/actions/runs/6002291906

---------

Co-authored-by: robot-ci-heartex <robot-ci-heartex@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants