Rodrigo López Dato

Thanks, updated this PR to be a draft until I can get back to it.

To anyone running into this issue, you should be able to work around most of the configuration limitations of this action by adding a `.fossa.yml` file to the same directory...

@revtut This makes sense to me - it would be consistent with what we're doing already for other SDKs. For example: * Node.js: https://github.com/Flagsmith/flagsmith-nodejs-client/blob/a2a3c1c997b5f9a7478627ae7029577667fc6555/sdk/analytics.ts#L54-L58 * Java: https://github.com/Flagsmith/flagsmith-java-client/blob/9f506f41007b21b7f0a90dcaa12069a7245fe581/src/main/java/com/flagsmith/threads/AnalyticsProcessor.java#L127-L135 * Android: https://github.com/Flagsmith/flagsmith-kotlin-android-client/blob/c49f0884eea59775e6ce4395bd05a2ce3f45d7df/FlagsmithClient/src/main/java/com/flagsmith/internal/FlagsmithAnalytics.kt#L25-L30...

Instead of adding the protected tag to all projects on the backend, have we considered showing `protected` as an option anyway from the frontend if it wasn't returned by the...

Re-opening - this was automatically closed by #4061 but that PR was just for the optional labels.

> Closing this since we have the 'is permanent?' toggle on flags now Where is that in the UI/docs?

Sorry, that's exactly what I was trying to get at in this issue. There should be a default "protected" option that exists for this case. It makes no sense IMO...

Another more intrusive option would be to remove permanent-ness from tags altogether, and have it as a boolean option per each feature. This is something that users should decide at...

> we should just add the link to the existing change request alert That was next on my list of feedback :) I agree adding the link(s) to change requests...

I can't think of anything feasible besides a tree-style editor to build arbitrarily complex boolean conditions, similar to https://querybuilder.js.org/ but with an actually nice design :) This will likely require...