This callback is usually involved any time another system might need
authentication. As such, you are expected to provide a valid
git_credential object back, depending on allowed_types (a
git_credential_t bitmask).
Note that most authentication details are your responsibility - this
callback will be called until the authentication succeeds, or you report
an error. As such, it's easy to get in a loop if you fail to stop providing
the same incorrect credentials.
@param out_ The newly created credential object.
@param url The resource for which we are demanding a credential.
@param username_from_url The username that was embedded in a "user\@host"
remote url, or NULL if not included.
@param allowed_types A bitmask stating which credential types are OK to return.
@param payload The payload provided when specifying this callback.
@return 0 for success, < 0 to indicate an error, > 0 to indicate
no credential was acquired
Credential acquisition callback.
This callback is usually involved any time another system might need authentication. As such, you are expected to provide a valid git_credential object back, depending on allowed_types (a git_credential_t bitmask).
Note that most authentication details are your responsibility - this callback will be called until the authentication succeeds, or you report an error. As such, it's easy to get in a loop if you fail to stop providing the same incorrect credentials.
@param out_ The newly created credential object. @param url The resource for which we are demanding a credential. @param username_from_url The username that was embedded in a "user\@host" remote url, or NULL if not included. @param allowed_types A bitmask stating which credential types are OK to return. @param payload The payload provided when specifying this callback. @return 0 for success, < 0 to indicate an error, > 0 to indicate no credential was acquired