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.
Create a separate commit for builds, much easier to merge/rebase
See original GitHub issue@shockey @bodnia @webron
The /dist folder often comes into merge conflicts, making feature branches difficult to keep clean and up to date.
Is it possible to enforce a rule ( "enforce "), whereby the build happens on its own commit? That way an interactive rebase becomes a smooth operation ( since we just ignore all those build commits, which are useless in a rebase ). The ends are still met, where we have dist built, and in the PR it’ll merge happily
Ultimately just our internal practice and a mention in the README?
Food for thought, I can add the note in the readme - if this makes sense.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 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
CONTRIBUTING it is.
👍
I already do this. Let’s consider codifying this in the README?