https://bugzilla.redhat.com/show_bug.cgi?id=2142391

M Hickford <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Comment|0                           |updated



--- Comment #0 has been edited ---

Spec URL:
https://raw.githubusercontent.com/hickford/git-credential-oauth-rpm-spec/main/git-credential-oauth.spec
SRPM URL:
https://download.copr.fedorainfracloud.org/results/matthickford/git-credential-oauth/fedora-rawhide-x86_64/05063649-git-credential-oauth/git-credential-oauth-0.1.5-1.fc38.src.rpm
 
COPR: successful build
https://copr.fedorainfracloud.org/coprs/matthickford/git-credential-oauth/package/git-credential-oauth/
Description: A Git credential helper that securely authenticates to GitHub,
GitLab, BitBucket and other forges using OAuth. The first time you push, the
helper will open a browser window to authenticate. Subsequent pushes within the
cache timeout require no interaction.
Fedora Account System Username: matthickford

FE-NEEDSPONSOR. I'm the upstream maintainer if it counts for anything:
"Sponsors can also decide to accept an applicant based on other types of
contributions. For example, the applicant may be the upstream maintainer for
the project"
https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_policy/#other_contributions

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2142391
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to