Search for a command to run...
Use GitHub Actions to automatically repost from Hashnode to DEV
No comments yet. Be the first to comment.
In this series, I walk through two ways to re-syndicate your blog posts from Hashnode to DEV.
RSS for the win!
Two ways to make pop-up images in a Google Sheet
Since last we spoke I’ve been recording several new long and short form videos. Check out the YouTube Channel if you haven’t. I’ve also wrapped up training for a marathon I’ll be racing on March 3rd… 🤞🤞 Now to the sheets… Do you ever feel lost in E...
Originally published for freeCodeCamp In this article I will show you how to allow for multiple items to be selected using the drop-down data validation feature in Google Sheets. Here's the Google Sheet we'll use for the example. You can make a copy...
Originally published for freeCodeCamp Without clean data, your spreadsheet is knocking on death's door. In this tutorial, I will show you two fast ways to clean up the data in your Excel or Google Sheets spreadsheet. When dealing with data sets, esp...
Originally published for freeCodeCamp In this article I will show you how to format cells in Microsoft Excel. We'll be looking particularly at the Accounting format for cells with numbers. At the end of the article I'll give you two bonuses: a short...
Here's my article about the easier way to do all of this via an RSS feed import. It was still fun to learn about GitHub Actions and set things up, so feel free to keep reading and explore this more laborious route as well!
You'll want to backup your @Hashnode articles to your GitHub account first. I wrote about how to do that here and it's pretty easy to do.
Go here and grab an API key. This is the only setup you need over on DEV.
Don't share the API key! 😁
If you, like me, have never used GitHub Actions, let me break down a few things as I am learning in real time too.
Actions will "Automate your workflow from idea to production". Here's the features page from GitHub.
It's just a way to automate stuff that needs to happen. Events are triggered when you make a commit to your repository. For us, it's perfect since we want a commit to our Hashnode backup repository to trigger a new post to be made over on DEV.
Here is the publish-devto Action on the GitHub Actions Marketplace. It is not certified by GitHub and is provided by a third-party.
This was created by Yohan Lasorsa.
Here is the repo for the publish-devto Action.
It works by "delegat[ing] most of the work to the devto-cli push command".
The directions for Actions live inside a .yml file at yourRepo/.github/workflow/publish.yml.
Below is the complete .yml from the sample devto-github-template.
# This workflow will push and update articles on dev.to each time a new
# commit is pushed to the main branch.
#
# To make it work, you need a dev.to API key, see:
# https://developers.forem.com/api/#section/Authentication/api_key
#
# Once you have generated the token, you need to add them as a secret in your
# GitHub repository:
# - DEVTO_TOKEN: your dev.to API key
# See https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets
# for more information about GitHub secrets.
name: publish
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
publish:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Publish articles on dev.to
uses: sinedied/publish-devto@v2
id: publish_devto
with:
# Your dev.to personal API key to publish and update articles.
# See https://docs.dev.to/api/#section/Authentication/api_key
devto_key: ${{ secrets.DEVTO_TOKEN }}
# Your GitHub personal access token, used to create commits for updated files.
# If you have a protected branch, you need to use a personal access token
# with the 'repo' permission.
# See https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
github_token: ${{ secrets.GITHUB_TOKEN }}
# (Optional) The files to publish. Default is "posts/**/*.md"
files: 'posts/**/*.md'
# (Optional) The git branch to use. Default is 'main'.
branch: main
# (Optional) Use conventional commit messages. Default is false.
# See https://www.conventionalcommits.org.
conventional_commits: true
# (Optional) Do not make actual changes on dev.to if it's a pull request.
dry_run: ${{ github.event_name == 'pull_request' }}
# (Optional) Add comment with dev.to changes if it's a pull request.
- uses: actions-ecosystem/action-create-comment@v1
if: ${{ github.event_name == 'pull_request' }}
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
body: |
Changes result:
```
${{ steps.publish_devto.outputs.result_summary }}
```
You can clone and use the devto-github-template, however because Hashnode has us setup to backup straight to the root of our backup repository, we'll need to change a couple things.
I'm going to create the .github/workflows/publish.yml myself rather than cloning anything. If you've copied the contents of the devto-github-template, you'll want to change the files: line to reflect where all the Hashnode articles live in the repo.
I neglected this part at first, and was met with errors. I'm grateful to Yohan, the author of the publish-devto, for taking the time to do some troubleshooting with me!
You'll need the front matter to contain at least a title for the Action to recognize the post. Here is the example post from the devto-github-template.
And, as you'll see in the issues section at the bottom of this article, you'll probably want to include the published: true line below as well.
---
title: Example article title
published: false
description: A simple test article
tags: 'productivity, beginners, test'
cover_image: ./assets/cat.jpg
canonical_url: null
id: 853728
---
Some random text with a [link](https://code.visualstudio.com).
After having posted to Hashnode, grab the url of the published article so you can include this in the front matter for DEV.
Honestly, this front matter stuff is the only real hiccup part. In the current state, we'll need to edit the markdown file on GitHub in order for this to work. And doing that is a step in an otherwise seamless automation. I suspect this is something that could be added. I may do some more digging, but for now: onward!
You need to plug a couple things into the GitHub Hashnode Backup Repo as secrets. This is where you'll put your API key from DEV and your personal access token from GitHub.
Make a new secret named DEVTO_TOKEN and paste your DEV API key into the value. If you have a protected branch, you'll need to do the same for GITHUB_TOKEN as a new secret:
You should be good. I am making a small change to one of my previous posts and then adding the front matter to see if it properly triggers the action on my account now...
After a bit of confusion, I found that GitHub has a status page, and that Actions are currently experiencing issues! If you happen to be doing this and not triggering the workflow action at all, check out the status page before melting down! 😆
Excellent! This works, and should allow you to cross-post on DEV smoothly! Here's the link to my previous post on setting up auto-backups from Hashnode to DEV. That's half the job right there.
Note: When your post shows up on DEV, it will be a Draft. So you will have to go in and publish it there.
Remarkably, there doesn't seem to be a way to publish it from the web app. I believe it's because of the front matter we added. If you recall above, there are some other values for the front matter including a published: optional value. Apparently, if it's not there, it will default to false.
I added a true value to my next test article, and voila! It worked like a charm!
Here's one of the first articles over on DEV that I successfully imported using this method.
Let me know if you find any issues or better ways to do this! Also, if anyone has it setup the other way: from DEV to Hashnode, I'd be interested in checking that out too.
Would you share this article for me? I'm building my personal content portfolio and every exposure is helpful! Thanks a ton!
You can find me over on Twitter; I'd love to say hey!