-
-
Notifications
You must be signed in to change notification settings - Fork 5
feat: Bluesky support #32
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
feat: Bluesky support #32
Conversation
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 is important to document this in the README, just like the other supported services. Otherwise, end users will have no idea Bluesky support exists unless they read through the source code.
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.
Other than squashing these commits (which can be done by a maintainer at merge time), this looks good to me.
@lgiordani: Any thoughts?
|
Hey, sorry for the delay! Nope, all good on my side, I'll squash and merge now |
|
Thanks @weeheavy for the contribution! |
|
Can you cut a pypi release for this? |
|
Apologies, I completely forgot to do that. I'm doing it with #33 |
|
@kjoconnor It's done, you can find release 1.2.0 at https://pypi.org/project/pelican-share-post/ |
|
Thank you! |
Added support for Bluesky Action Intent Links (https://docs.bsky.app/docs/advanced-guides/intent-links)