-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: set Asana to milestone based on PR milestone #44
Conversation
0987417
to
7113822
Compare
08d8ed9
to
cbef573
Compare
8a95be3
to
e0e7c1f
Compare
1999f82
to
8d7ec84
Compare
@dooglio Thanks for the suggestion, amigo! Updated and tested. I created a release |
@federico-po I'm interested to see how it goes in testing! |
Definitely! Feel free to follow the test plan and also I added a DEMO video (originally created for Josh so please skip the first 2 mins 😝 ) |
See this PR: |
…#51) * chore: remove node_modules * build: add @vercel/ncc for packaging * build: add .nvmrc * build: move supporting js files into `src` * build: add `build` step and package dist release * build: switch to node16 * build: add husky pre-commit hook to run build Co-authored-by: Federico Ponce de Leon <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
Summary
This PR sets the milestone in the asana tasks' linked in the PR.
Once a PR has at least one Asana task linked, and a milestone is set to the PR, the automation will run and will try to set the same milestone in the task that in the PR.
e.g. (covered by tests):
Note:
The automation will assume that:
Target Release Version
field.asana_milestone_field_name
in the GitHub action.gh_milestone_regex
in the GH action.asana_milestone_regex
in the GH action.Closes: this Asana task.
Test Plan
asana-actions-workflow
(a console.log for example)federico/link-asana-milestone
Closes:
prefix.DEMO
Further Comments
Ok GH actions are a bit tricky.
Milestoned
andDemilestoned
are triggered at the same time when you switch from Milestone X to Y, so they get overwritten each other and usually the tasks end up withnull
(empty milestone). I added a delay of 15 secs for milestoning the task. This ensures that milestoning tasks await for some secs until demilestone happened (in case it's a re-milestoning)