feat: Allow Project and Task GID to be provided to the action#21
Open
muddy-alex wants to merge 2 commits intoAsana:mainfrom
Open
feat: Allow Project and Task GID to be provided to the action#21muddy-alex wants to merge 2 commits intoAsana:mainfrom
muddy-alex wants to merge 2 commits intoAsana:mainfrom
Conversation
feat: Accept Task and Project GID
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
1 participant
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 appreciate this one is a slight hack to get working as it basically constructs an Asana link and submits it to the API as the pr description.
It negates a bit of faff in copy/pasting asana link as we utilise GID's (and incrementing Id's in our Tasks) in branch names and means we can use it alongside other actions that interface with the Asana API which accept Task GID's.
I'm sure a change to the backend would be the more appropriate resolution, but this has been working great for us and seems the community would like something similar. (i.e #7)