Stage constraint ordering#193
Merged
Merged
Conversation
qweliant
force-pushed
the
qdt/make-stage
branch
from
f3cc5b9 to
75b11a5
Compare
qweliant
force-pushed
the
stage-constraint-ordering
branch
from
3fcc8c6 to
6c24d84
Compare
…kflows, consolidate functions
3mcd
approved these changes
Dec 4, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue(s) Resolved
Solves part of #190
Test Plan
Navigate to
stages/dashboardand check that the tabs are ordered as expectedNavigate to
stages/and be sure that stages are ordered as expectedScreenshots (if applicable)
Optional
Notes/Context/Gotchas
Stages are now ordered as they move through a graph. This does not render sperate workflows. We should think about how that looks in a settings page and stage page
Supporting Docs