Search for a command to run...
Keep your community up to date with the latest releases
I'm Manuel and I work at NearForm as a Full Remote Software Developer from 🇮🇹 Italy. I'm one of the Fastify maintainers since 2019. Contributing to Open Source Software teaches me something new every day. You should join this extraordinary world.
Great article! One question though, what callback URL we need to give while create Twitter App with OAuth 2.0?
I assume you are tralking about this setting:
You don't need to set up that parameter because the authentication between GitHub Action and Twitter is established by the API Keys
How to stream React components to the browser using Fastify and reply.hijack()
Did you see the "Verified" badge on some GitHub commits and wonder how to get it for your own commits? Well,GitHub shows the ‘Verified’ badge when a commit has a valid signature from a trusted key (GPG, SSH, S/MIME, or GitHub’s own). In this article...
Part 0: From Instinct to System
We share smart strategies for ensuring a slow client doesn’t crash your server
I was looking at the Fastify plugin list and found myself asking, "What is this @fastify/request-context plugin?"So, I checked it out, and here I am, writing a post about it to share what it is and how it can be useful for you! What is AsyncLocalStor...
One of the most boring things for a developer to do are repetitive tasks. All these tasks can be automated because it does not require concentration or your skills. Unfortunately, you don't have time to automate those tasks.
For example, you want to inform your team about a new release, but you don't have time to do it, or you forget about it.
Here you are a simple way to do it, thanks to GitHub Actions!
You need to stop doing repetitive tasks and start doing something useful for your team. So ask yourself:
These questions are the ones you need to answer.
The when question identifies the git repository event you want to listen to.
The which question identifies the information you want to send.
The how much question identifies if you should create an application and sell it 🤑
We are going to answer these questions with a simple example:
I want to send a tweet every time a new release is published on GitHub. The release schedule is flexible. I don't release more than a couple of times a day.
We can search for the suitable GitHub event from the Official Documentation.
First, you need to create a new workflow file into the .github/workflows directory.
The workflow depends on the event you want to listen to and the corresponding payload. All the JSON payloads can be found in the Official Documentation.
name: tweet-release
# Listen to the `release` event
on:
release:
types: [published]
jobs:
tweet:
runs-on: ubuntu-latest
steps:
- uses: Eomm/why-don-t-you-tweet@v1
# We don't want to tweet if the repository is not a public one
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 }}
As you can see, the workflow is straightforward. It requires:
tweet-message variable to be set with the message you want to send. Note that if you overflow the 280 characters limit, the action will fail.env keys to send the tweet on your behalf.You need to create a Twitter App using the Twitter Developer Portal. The GitHub Action works with Twitter API v2.0, so the free plan is enough.
After creating the App, you will get the secrets:
TWITTER_CONSUMER_API_KEYTWITTER_CONSUMER_API_SECRETStore them in a secure place: you will need them to send the tweet.
Then, from the App details page, you need to change the App Permissions from read to read and write:
Now you need to do the last step.
From the Keys and tokens menu, you need to create two more keys:
TWITTER_ACCESS_TOKENTWITTER_ACCESS_TOKEN_SECRET
These two keys let the application posts a tweet using the authorized Twitter account.
Now you need to store those secret keys into your GitHub Repository secrets.
To test the tweet-release workflow, you need the create a new GitHub Release.
Creating a release was already one crucial step of your delivery process, and now you have automated the boring notification stuff!
This workflow works at its best within releasify!
This CLI tool creates a new npm version and a GitHub Release altogether, and publishing your module within this tool will trigger the tweet-release action!
Well done! You know how to increase your community involvement!
Do you want to read more? Subscribe to the backend.cafe newsletter!