I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
If I'm working on a bunch of separate features over a long period (which can happen with these personal projects...) it helps for me to queue them up as PRs so I can easily see what's going to go into the master branch.
If it's just one feature at a time I'll just merge it straight in instead.
I sometimes do.
If I'm working on a bunch of separate features over a long period (which can happen with these personal projects...) it helps for me to queue them up as PRs so I can easily see what's going to go into the master branch.
If it's just one feature at a time I'll just merge it straight in instead.
Thanks for the feedback - great insight! It seems to be best to create a PR when there is more than trivial changes!