feat(stability): remove nodes & flows that require too specific extra nodes #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bigcat88
force-pushed
the
feat/stability-security
branch
from
e72074c to
92505db
Compare
…tra nodes Signed-off-by: bigcat88 <[email protected]>
bigcat88
force-pushed
the
feat/stability-security
branch
from
92505db to
b18caaf
Compare
Signed-off-by: bigcat88 <[email protected]>
Signed-off-by: bigcat88 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had implemented this in the upcoming version of Visionatrix, the ability to exclude
flowsandcustom_nodes:These changes will make this integration more stable and lightweight. Also this will free some time, as there will be no need for me to check those repos with custom nodes for the new commits for every release.