Keeping context between calbacks

We have a `get-user-repo-access-info` procedure which is asynchronous - we run this in the `authenticate` callback as passed into the `Git` constructor. We do this to deny access to users before this library even looks for a git repo to use. However when we then get to the `push` event listener we're struggling to see how we can equate the original request with this specific callback. There is no shared state passed into the listener.

Would you be willing to help us rectify this? Honestly I'd be fine with just adding `http.IncomingMessage` to the `GitAuthenticateOptions` as `req` - I can then just add a property to that object :shrug:

It looks as though you've maybe kept the `authenticate` callback to accept the bare minimum of information though - if there's a specific reason for that perhaps we could add an empty `context` object to the `authenticate` callback which can then be passed to later event handlers. Avoiding giving the authenticate method any additional data to be mis-understood or used.

Thanks for the very helpful library, happy to open a PR for this, just wanted an idea of what is more likely to be merged.

首先跟踪传递给 Git 构造函数的 authenticate 回调以及后续的 push 事件监听器，重点关注 GitAuthenticateOptions 和提议的 context 或 req 数据。定义请求特定状态应如何在这些回调之间传递，然后验证身份验证和 push 处理能够关联同一个请求，同时不改变无关的 Git 操作。

由索引模型根据 Issue 内容生成。