logoalt Hacker News

Poogetoday at 12:10 PM1 replyview on HN

Why does the client have pushing rights to the repository? I would suggest working by pull request and approve all changes that they make. That's what you would do if you were working in a team.

If you work in a bigger structure, surely there is a product manager that can limit the scope of the project.

I would suggest to the client to develop their own tools that are to be supported by them exclusively while you continue supporting the "official" tools.


Replies

piscatortoday at 12:58 PM

Thanks for the suggestions. I've considered to protect some branches, but in the end decided against it. I was not looking forward to review all their huge amounts of slop code. It would also be different from reviewing code of a "real" developer. Feedback would normally be a way to help each other and improve as a team, and be received with a certain amount of gratitude or at least understanding. In this case, they would not read the feedback, at best they would feed it to a bot. They would see it as a needless obstacle. I agree to scope my parts of the project as much as possible. Then it might still be realistic to continue working on it.

show 1 reply