-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Description
Motivation
I'm in the process of rewriting all of our actions in Typescript in preparation of releasing v2.
| Name | PR |
|---|---|
publish-pr-preview |
#65, #69, #70, #71 |
synchronize-npm-tags |
#66 |
synchronize-with-npm |
#67 |
TODOs
-
I think we should also discuss the idea of renaming our actions - mainlysynchronize-with-npmbut might as well rename the other ones too:Old Name New Name synchronize-with-npmpublish-releasessynchronize-npm-tagssynchronize-tags?publish-pr-previewpublish-previews -
We have theyarnaction which we created in order to fail a workflow if there are any warnings duringyarn install. I don't think we need to keep that as a separate action. If we really wanted to incorporate that, we could do so within the other actions. Is it okay to omit this one from v2?- Delete yarn action from v2 and update table at root readme Track failed publish attempts for preview action #70
- Push current
mainbranch tov2to prevent any conflicts to workflows that are calling actions from themainbranch - Change base branch of remaining PRs to
v2 -
Once all actions are refactored, update all frontside projects to useDo this on a need-to basis@v2 - Update readmes to use v2 (the readmes are currently instructing to call the actions from
mainbranch) Track failed publish attempts for preview action #70 - Delete
mainbranch- These repositories need to update their workflows to migrate from
maintov2and we'll be able to delete themainbranch:-
thefrontside/element-is-visible#5 -
thefrontside/javascript#50 -
thefrontside/performance-api#6 -
thefrontside/microstates#426- If you scroll through here you should see they've all been updated (if the four PRs above have been merged)
-
- These repositories need to update their workflows to migrate from
Reactions are currently unavailable