Closed alexweininger closed 1 year ago
This feature request is now a candidate for our backlog. The community has 240 days to upvote the issue. If it receives 5 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!
:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!
When creating a new SWA from a given repo, if a repo already has a GitHub Action workflow yaml for deploying to SWA, we should try to re-use this workflow instead of creating a brand new one.
Currently, we always create a new one and it often results in two almost identical workflow files. However, one won't have the proper secrets in the fork so it will always fail.
Another benefit of this would be that any specific configuration from the existing workflow can be reused.