Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syncing only releases #77

Open
jdcrensh opened this issue Oct 24, 2017 · 4 comments
Open

Syncing only releases #77

jdcrensh opened this issue Oct 24, 2017 · 4 comments

Comments

@jdcrensh
Copy link

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 on master, 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?

  • Option to sync releases instead of choosing a branch, then use the API to find the latest release during sync.
  • Be less tied to what Github deems as a release, instead allowing configuration of an optional commit message regex, eg. ^Publish.*$. This would be easier to implement but less user friendly and prone to false positives.
@jdcrensh jdcrensh changed the title Syncing only releases or Syncing only releases Oct 24, 2017
@1egoman
Copy link
Collaborator

1egoman commented Oct 24, 2017

@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 #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!

@jdcrensh
Copy link
Author

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.

@1egoman
Copy link
Collaborator

1egoman commented Oct 31, 2017

@jdcrensh Here's a PR for #74: backstrokeapp/worker#2

@1egoman
Copy link
Collaborator

1egoman commented Dec 11, 2017

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants