You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
Hello!! this is an awesome project and it's great to have a smart workaround for the short comings of AWS Codepipeline.
Feel free to close this issue if the code already supports this workflow, but I am looking for something specific:
My company has decided on Gitflow, which requires the creation of 'release candidate' branches when code from 'develop' is deemed ready for release. Currently, I have to hardcode the release candidate branches name into our pipelines, which isn't ideal and will not scale well. I was hoping that AWS Codepipeline would support a wildcard feature where I can target for any branch that starts with 'release/', but of course, AWS doesn't support this.
Is it possible to implement a feature into this that looks for any new branch created that matches a certain regex pattern? (as opposed to any new PRs)
Thank you!!
The text was updated successfully, but these errors were encountered:
Hello!! this is an awesome project and it's great to have a smart workaround for the short comings of AWS Codepipeline.
Feel free to close this issue if the code already supports this workflow, but I am looking for something specific:
My company has decided on Gitflow, which requires the creation of 'release candidate' branches when code from 'develop' is deemed ready for release. Currently, I have to hardcode the release candidate branches name into our pipelines, which isn't ideal and will not scale well. I was hoping that AWS Codepipeline would support a wildcard feature where I can target for any branch that starts with 'release/', but of course, AWS doesn't support this.
Is it possible to implement a feature into this that looks for any new branch created that matches a certain regex pattern? (as opposed to any new PRs)
Thank you!!
The text was updated successfully, but these errors were encountered: