This is a great question that probably many developers have asked themselves before. Before recommending some ideas I will start out by mentioning what you should not do. If you need a break, take a break, maybe watch a little YouTube or catch up on a news article but don't make that a habit while waiting for your review to complete. This is what separates out the more mature developers. I have seen plenty of people slack off saying they are waiting for a review to finish and I must admit I have done that before as well.
Some ideas I would recommend.
1) If you don't want to fight future conflicts with your code, go and pick some work that is not related to your review. Then you can work on the new stuff without fear it will conflict with your existing work.
2) If you have broken up your work into sizable chunks (good for you, btw!) and you want to continue working while the review is out, I suggest you branch off from that commit. Then you can continue working off your existing work. If there are suggestions in the PR that require some changes, then make those changes and merge them back to the newly branched off code.
3) If you have no other work that needs your attention, go find something to improve in your system while you wait. Maybe do some performance measuring, or investigate some new tool or trick to enhance your software. Take this time to learn something new while you wait.
I hope these ideas help! Don't kill time but make the most of it while you have it.
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.
This is a great question that probably many developers have asked themselves before. Before recommending some ideas I will start out by mentioning what you should not do. If you need a break, take a break, maybe watch a little YouTube or catch up on a news article but don't make that a habit while waiting for your review to complete. This is what separates out the more mature developers. I have seen plenty of people slack off saying they are waiting for a review to finish and I must admit I have done that before as well.
Some ideas I would recommend.
1) If you don't want to fight future conflicts with your code, go and pick some work that is not related to your review. Then you can work on the new stuff without fear it will conflict with your existing work.
2) If you have broken up your work into sizable chunks (good for you, btw!) and you want to continue working while the review is out, I suggest you branch off from that commit. Then you can continue working off your existing work. If there are suggestions in the PR that require some changes, then make those changes and merge them back to the newly branched off code.
3) If you have no other work that needs your attention, go find something to improve in your system while you wait. Maybe do some performance measuring, or investigate some new tool or trick to enhance your software. Take this time to learn something new while you wait.
I hope these ideas help! Don't kill time but make the most of it while you have it.