post-import-utils/inject_blockers.py: Stop skipping resolved blockers.#106
Merged
semperos merged 2 commits intouseshortcut:mainfrom May 13, 2025
Merged
post-import-utils/inject_blockers.py: Stop skipping resolved blockers.#106semperos merged 2 commits intouseshortcut:mainfrom
semperos merged 2 commits intouseshortcut:mainfrom
Conversation
I had originally skipped resolved blockers because I didn't know how to represent the resolution state in Shortcut. Now I know (and like) that in Shortcut, a blocker has no resolution state of its own; rather, Shortcut infers the state of the blocker from the state of the blocking story.
…lockers.py` detects a claw in the blocker graph.
semperos
approved these changes
May 13, 2025
Member
semperos
left a comment
semperos
left a comment
There was a problem hiding this comment.
Thanks for updating the documentation as well, great to see blocking/blocked relationships better supported!
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.
I had originally skipped resolved blockers because I didn't know how to represent the resolution state in Shortcut.
Now I know (and like) that in Shortcut, a blocker has no resolution state of its own; rather, Shortcut infers the state of the blocker from the state of the blocking story. Therefore, we can use identical Shortcut API operations to write blockers from Pivotal, regardless of their Pivotal resolution state.