Pre-commit hook running remotely on the forge "before they push" sounds like an oxymoron. How does the code get to the forge for feedback? That's a post-push hook!
> Pre-commit hook running remotely on the forge "before they push" sounds like an oxymoron.
I think the implication is that a user doesn't host the CI locally. They are suggesting that there should be? a configuration to call an API to submit the code changes for some part/total CI checking. This is only beneficial for orgs/individuals which somehow rank dev effectiveness based on how messy a branch PR history is and how many times they have submitted code that passes/fails a build. Maybe due to build cost, maybe due to ego.
I understand what they are asking for, but it feels like misusing git or based on some org process rather than normal development flow. I don't understand the point.
Right, wrapping the response in blockquote and one extra sentence providing context would have helped there. Other people on the issue got confused by this as well (same for me but it got clearer when I read further on).
reply