I do the same! Issues and pull requests on Github is a very handy tool to improve productivity and stay aware of the project, even not working in a time on that repo.
I'm trying something in a few weeks that works a ton for me, I usually do like this:
Create a branch signing with is a feature/bugfix/hotfix an then the folder following by the current change
feature/cartModule/cartList
Do what is necessary on project, and go for a commit. Here is a awesome stage that I recommend the most
All set up, then I merge to master, always set this branch up to date
I find super useful in this merge process: code review! in each final merge, I review what is done and anything that comes in my mind, I comment on the lines or review the entire merge
I think that is a good way and you have all the information within the repo, not having writhing elsewhere that you can easily forget
Any ideas to improve is very welcome!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A little addendum:
I do the same! Issues and pull requests on Github is a very handy tool to improve productivity and stay aware of the project, even not working in a time on that repo.
I'm trying something in a few weeks that works a ton for me, I usually do like this:
feature/bugfix/hotfixan then the folder following by the current changefeature/cartModule/cartListDo what is necessary on project, and go for a commit. Here is a awesome stage that I recommend the most
All set up, then I merge to master, always set this branch up to date
I find super useful in this merge process: code review! in each final merge, I review what is done and anything that comes in my mind, I comment on the lines or
reviewthe entire mergeI think that is a good way and you have all the information within the repo, not having writhing elsewhere that you can easily forget
Any ideas to improve is very welcome!