Enhance: Add Bluesky share link to merge message #91659
Conversation
|
Hi, I noticed my contribution is not appearing as expected. Could you confirm if the workflow executed correctly, or if there’s anything I need to fix? Thank you! |
What's your expectation?
It's not executed. For security, fork pull request workflows aren't run. For testing, try it on your fork. |
|
I’ve updated the merge message to include Bluesky share links with hashtags (#OpenSource, #FirstContributions) and formatted them as a bulleted list. Let me know if further updates are needed! |
| - Continue contributing: Check out our [<img src="${repo_logo}" width="22" title="web app" /> webapp](${web_url}). | ||
| - Join our Slack group: [<img src="${slack_logo}" width="22" title="Slack" /> Join Slack group](${slack_invite_url}). | ||
| - Share on social media: | ||
| - [<img src="https://cdn.jsdelivr.net/npm/supertinyicons/icons/twitter.svg" width="22" title="Twitter" /> Share on Twitter](https://twitter.com/intent/tweet?text=I+just+contributed+to+First+Contributions!+Check+it+out:+https://github.com/firstcontributions/first-contributions+%23OpenSource+%23FirstContributions) |
There was a problem hiding this comment.
Formatting looks correct now, but now we're missing a few options we had before (dev.to, hackernews, facebook)
We have the links and logos declared above. Lines 95 to 115. Could you please reuse those.
I think it would be good if Bluesky share is the first one.
Also, could you please test the workflow on your fork and share that PR in comments?
This PR adds a Bluesky share link to the GitHub Actions merge message to increase social sharing options for contributors. Fixes #91497.