4 ms·
Personally, I tend to post the change in a comment on the issue that it fixes. I don't generally bother with doing a formal PR, since that would mean setting u
by jasonkester 5y ago
Personally, I tend to post the change in a comment on the issue that it fixes. I don't generally bother with doing a formal PR, since that would mean setting up the repo in a dev environment, branching, etc. and would be a bunch of extra work.
Locally, I just make the change and check it in to my project.
Here's an example:
https://github.com/xwpongithub/vue-range-slider/issues/3#issuecomment-544900793 https://github.com/xwpongithub/vue-range-slider/issues/3#iss...
- PetahNZ 5y agoYou can literally edit the file in github and submit a PR with a few clicks.
- resizeitplz 5y agoEvery repo has different contribution rules and a one-off in one repo often just isn't worth the time to learn all the bespoke boxes that need to be checked. The work is there in the comments and if it's of value, someone more familiar can take it the last mile ... and codespaces _just_ came out generally. Could you edit online before that?