Open jdcrensh opened 7 years ago
@jdcrensh Cool idea!
Once requirement is that Github requires pull requests to be made off of a branch, which would make pull requests off of tags a bit hard. I'm exploring https://github.com/backstrokeapp/server/issues/74, which could potentially make syncing to a tag possible.
A commit message regex would definitely be easier, though an inferior solution.
Is this a feature you'd like to work on? This isn't something that I would likely work on in anytime soon.
Thanks for the idea!
I hadn't considered that limitation of PRs, thanks for pointing it out before I spent too much time on it. May have some time to explore it in a week or so, but I'll watch #74 cause it might be a prerequisite.
@jdcrensh Here's a PR for #74: https://github.com/backstrokeapp/worker/pull/2
@jdcrensh That PR I previously mentioned has been merged. Don't know if this is still something you're interested in working on but if so the backend code for that feature is in a good place.
Backstroke is great for syncing commits from a branch. But in certain situations, it'd be ideal to create backstroke PRs only for upstream releases.
Taking
create-react-app
as an example, I don't really want to have Backstroke create a PR for every other commit onmaster
, because the changes may not be ready for production. I'd want to have a PR created whenever a release is cut.What would be the best approach here?
^Publish.*$
. This would be easier to implement but less user friendly and prone to false positives.