Add bluesky to OpenScPCA footer #989
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you @dvenprasad! Merging is currently blocked. Do you know if both code owners must review every PR? (I don't think I have filed one in this repo for quite awhile!) If not, maybe I need to re-request you to approve this. |
jaclyn-taroni
approved these changes
Jan 16, 2025
|
Deepa did not actually approve, just commented – that was the issue. I've now approved. |
|
Ah ok! Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose/implementation Section
I am adding our new Bluesky account to the OpenScPCA website footer. (I deleted most of the instructions in this template since it's not that kind of contribution!)
Please link to the GitHub issue that this pull request addresses.
This PR addresses #986.
What is the goal of this pull request?
See above!
Provide directions for reviewers
I'm not sure if there was more to do beyond editing the social section in
mkdocs.yml. Let me know if more steps are required for this! (I think it's fine if only @dvenprasad reviews this.)