Feature: Monorepo management

[bdougie]

Type of feature

Build

Current behavior

This repo is a monorepo. We need some sort of sane way to manage this project and organize the contents.

Open to suggestions.

Questions

• How do we handle esm powered actions?
• Should each action have its own package.json?
• What happens if one action includes typescript? How is that going to be manage? (might never happen, but just a thought)

Desired solution

Honestly, would love to know if there other folks using actions in this way we can get ideas from.

• Lerna is an option
• npm workspaces
• https://github.com/babel/actions

Additional context

mentioned on stream 2/24/21

Code of Conduct

• I agree to follow this project's Code of Conduct

[mtfoley]

May be worth noting that since this is a monorepo, we may not be able to publish to marketplace.

https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace#about-publishing-actions

From this, a marketplace published action is one-to-one with a GitHub repo.

Also tried implementing a typescript action in the repo over at https://github.com/nickytonline/epic-actions , and got super hung up on pre-commit hooks with it.

[glimow]

For the management of pre-commit hooks you might wanna check https://github.com/Escape-Technologies/mookme