-
-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for GitHub recipient #64
Conversation
Doesn't #43 supercede this by being more generic? |
Yes, that's true. That PR likely needs support for "github:username" syntax, otherwise it supercedes. But this PR can be closed if that's going to be used! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better if
- parsing a JSON is avoided, as
https://github.com/user.keys
gives already the result needed - this PR builds on top of Get recipient keys from https:// and file:// URLs #43, making
github:user
an alias tohttps://github.com/user.keys
Hi! Thank you for contributing! I took a different path in #173, but it was useful to look at open PRs for the users' expectations. Let me know if that implementation works for you! I wrote up an explanation of why I ended up implementing recipient files and not HTTPS sources on the mailing list, and I appreciate feedback! https://groups.google.com/g/age-dev/c/StmWsOyb-H8/m/a44rSBIWCAAJ |
This PR adds support to fetch user public keys directly from Github API. (edit: seems to be duplicate of #43)