Skip to content

New and Improved Frontside Actions v2 #68

@minkimcello

Description

@minkimcello

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 - mainly synchronize-with-npm but might as well rename the other ones too:
    Old Name New Name
    synchronize-with-npm publish-releases
    synchronize-npm-tags synchronize-tags?
    publish-pr-preview publish-previews
  • We have the yarn action which we created in order to fail a workflow if there are any warnings during yarn 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?
  • Push current main branch to v2 to prevent any conflicts to workflows that are calling actions from the main branch
  • Change base branch of remaining PRs to v2
  • Once all actions are refactored, update all frontside projects to use @v2 Do this on a need-to basis
  • Update readmes to use v2 (the readmes are currently instructing to call the actions from main branch) Track failed publish attempts for preview action #70
  • Delete main branch

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions