> That doesn't make sense to me.
1. Navigate your browser to GitHub.mycompany.example.com
2. Click the repo name
3. Click pull requests
4. Click the source branch[1] and destination branch
5. Click "create pull request"
???
I started out by assuming this was some kind of good-faith disagreement, but I guess you're just trying to be funny.
[1] Presumably already extant, because they never mentioned anything about committing code, nor pushing it to github (and that's not the same operation!).
The OP said:
"we also ask the candidate to open a PR"
So I think the OP meant to have the candidate, um, open a PR. Which is not the same thing as making a commit and pushing it to a remote. Maybe you always conflate those operations, but that doesn't make them the same operation. If the OP actually meant "make a commit, push it to the remote, and then open a PR", I would have expected the OP to say, um, all of those things, instead of just the last one.
I couldn't say how the OP expected the candidate to open a PR, since I don't know what their standard workflow is. There are ways of doing it from the CLI, as well as through the web interface, as well as through various IDEs.
> I started out by assuming this was some kind of good-faith disagreement, but I guess you're just trying to be funny.
Please save your patronizing for another time. And stop trying to put words in my mouth.
This makes it seem like all of those things are part of a single operation to you. That doesn't make sense to me.
On the occasions where I've submitted a PR to a project (anywhere, not just on Github), making the commit was not part of the same operation. I'd already made the commit and satisfied myself that it captured everything I wanted, before making the PR. I don't see those things as part of a single operation. I don't think the poster you were responding to does either.