Closed
Description
Summary
In the GitHub Organization we have a repository that should be dedicated to GitHub Actions, these are custom actions that can be shared across repos without having to be published to the GitHub Marketplace.
Currently we have a custom action that manages the node_modules
cache and optionally builds the project. This action could be used across any of the repos that use Node.js and has already been replicated to the central action repo.
We should remove the one we have here and point to that one instead.
Why is this needed?
So that we can start centralizing some of the GitHub Actions and use them across repos.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Shipped