keufran

Thanks for sharing. I'll do my best to do a follow-up.

Nice and simple idea ! Thank you

Yes, I clearly need to understand his actual workflow to know where (and how) to "hook" the review process. Thank you for the feedback.

I wasn't aware of these tools. I will have a look on them, thank you very much.

Thank You @lbotos; I will email you as soon as I'm back to work.

I hope Gitlab will fix this (it really should) but I need a solution in the meantime...

You're absolutly right, and I'm looking to improve this. However this is not the only pain point. The amount of remarks you can do in a code review can be huge, and I don't expect my coworker to be able to remind all what I say. So I also need a "place" where to put the remarks that he could refer to at his own pace.

You're welcome. It's great if just raising the question help other people :)

No I didn't. I even don't check for myself if accessibility is really bad, but I trust my coworker on this.

No, I don't review all team's code. A point is that he will work alone on a very specific piece of code. He is junior on the technology, so I'll review mostly for educational purpose.

OK. Thank for the tip, we will try.

Yes, of course he will be involded by suggesting, trying and validating the solutions.

Software Craftsmanship from mancuso helped me a lot to find meaning in my work as a software devloper