Syncing only releases
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start with the issue description and examine how Backstroke currently selects an upstream branch and determines when to create a PR. Compare GitHub release-based syncing with an optional commit-message pattern, then clarify the intended configuration and behavior. Done means the chosen release strategy is specified and its edge cases are covered.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- JavaScript
- Stars
- 663
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from backstrokeapp/server
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
backstrokeapp/server#93 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
backstrokeapp/server#92 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
backstrokeapp/server#90 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
backstrokeapp/server#88 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
backstrokeapp/server#85 · 2 comments ·
All issues in backstrokeapp/server
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·