Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MNT: Have a bot to auto-backport as PR
See original GitHub issueWhen a PR against master is merged, it would be desirable to have a bot to automatically open up follow-up PR(s) to backport changes that are just merged against older release branch(es), depending on the relevant PR milestone.
If the automatic backport PR(s) encounter difficulties, such as failed CI or conflicts, the bot should then take follow-up actions (apply special labels or create comments) so that manual intervention can be done.
If possible, we should not “roll our own,” but rather look at how other major projects are doing their backports, and see how we can reuse existing solutions. If all fails, @Cadair said he has a special hack that works “half the time”…
It is something we should aim for sooner than later, so I am going to add a milestone to this issue.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:22 (21 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m Mr. Meeseek, @saimn, Look at meee !
@pllim, is this closed by the meeseeksdev bot?