Send a tweet from a GitHub actions workflow!
To allow GitHub Actions to send tweets programmatically, you'll need to:
- Create a new Twitter application from your developer console.
- Turn on the Read and Write permissions
- Configure the authentication keys and tokens for your Twitter app as secrets in your repository.
- Add the
Usagesection code to your workflow's.
Done in 10 minutes 🎉
This configuration lets you to tweet using your Twitter account.
TWITTER_CONSUMER_API_KEY: the application consumer key.TWITTER_CONSUMER_API_SECRET: the application consumer secret.TWITTER_ACCESS_TOKEN: your user access token, generated from the developer console.TWITTER_ACCESS_TOKEN_SECRET: your user access token secret, generated from the developer console.
Copy & Customize the following code into your workflow:
name: tweet-release
# More triggers
# https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#release
on:
release:
types: [published]
jobs:
tweet:
runs-on: ubuntu-latest
steps:
- uses: Eomm/why-don-t-you-tweet@v2
if: ${{ !github.event.repository.private }}
with:
# GitHub event payload
# https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#release
tweet-message: "New ${{ github.event.repository.name }} release ${{ github.event.release.tag_name }}! Try it will it is HOT! ${{ github.event.release.html_url }} #nodejs #release"
env:
# Get your tokens from https://developer.twitter.com/apps
TWITTER_CONSUMER_API_KEY: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
TWITTER_CONSUMER_API_SECRET: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
TWITTER_ACCESS_TOKEN: ${{ secrets.TWITTER_ACCESS_TOKEN }}
TWITTER_ACCESS_TOKEN_SECRET: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}This workflow is ready to use within the releasify CLI!
Give it a try!
Read the developer documentation.
Copyright Manuel Spigolon, Licensed under MIT.