You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the merging of #56, Megamind work items will now be tracked through stories and overall project progress will be tracked on the Megamind project. Even with this new formality there are still some areas of manual effort. For example, linking PRs to the issues which the story is linked to, since as of now Github does not support linking issues with other issues directly through verbs, like, closes.
I'd like to use this forum to identify some processes which could be automated with Github Actions.
My automation suggestions
Parse story description for linked issues and link PR to those issues also so they're auto closed when the PR is merged.
If a story gets created without being assigned to the Megamind project, then assign it and set its status to "Refinement"
documentationImprovements or additions to documentationfeatureNew feature or request
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
With the merging of #56, Megamind work items will now be tracked through stories and overall project progress will be tracked on the Megamind project. Even with this new formality there are still some areas of manual effort. For example, linking PRs to the issues which the story is linked to, since as of now Github does not support linking issues with other issues directly through verbs, like, closes.
I'd like to use this forum to identify some processes which could be automated with Github Actions.
My automation suggestions
Beta Was this translation helpful? Give feedback.
All reactions