1. Star this repo 😉

2. Go to your repository

3. Add the following section to your README.md file, you can give whatever title you want. Just make sure that you use <!-- BLOG-POST-LIST:START --><!-- BLOG-POST-LIST:END --> in your readme. The workflow will replace this comment with the actual blog post list:

   # Blog posts
   <!-- BLOG-POST-LIST:START -->
   <!-- BLOG-POST-LIST:END -->

4. Create a folder named .github and create a workflows folder inside it, if it doesn't exist.

5. Create a new file named blog-post-workflow.yml with the following contents inside the workflows folder:

   name: Latest blog post workflow
   on:
     schedule: # Run workflow automatically
       - cron: '0 * * * *' # Runs every hour, on the hour
     workflow_dispatch: # Run workflow manually (without waiting for the cron to be called), through the GitHub Actions Workflow page directly
   permissions:
     contents: write # To write the generated contents to the readme
   
   jobs:
     update-readme-with-blog:
       name: Update this repo's README with latest blog posts
       runs-on: ubuntu-latest
       steps:
         - name: Checkout
           uses: actions/checkout@v4
         - name: Pull in dev.to posts
           uses: gautamkrishnar/blog-post-workflow@v1
           with:
             feed_list: "https://dev.to/feed/gautamkrishnar,https://www.gautamkrishnar.com/feed/"

6. Replace the above URL list with your own RSS feed URLs. See popular-sources for a list of common RSS feed urls. Commit the changes.

7. Go to repository settings, Click on Actions > General. Update the "Workflow permissions" to "Read and write permissions". Click on save.

   

8. Wait for it to run automatically, or you can also trigger it manually to see the result instantly. To trigger the workflow manually, please follow the steps in the video.

This workflow has additional options that you can use to customize it for your use case. The following are the list of options available:

Click to expand:

name: Latest stack oveflow activity
on:
  workflow_dispatch:
  schedule:
    - cron:  '0 * * * *'
permissions:
      contents: write
jobs:
  update-readme-with-blog:
    name: Update this repo's README with latest activity from StackOverflow
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gautamkrishnar/blog-post-workflow@v1
        with:
          comment_tag_name: "STACKOVERFLOW"
          feed_list: "https://stackoverflow.com/feeds/user/4214976"
          template: "<tr><td>$title</td><td>$url</td></tr>"

### Latest StackOveflow activity of [@gautamkrishnar](https://github.com/gautamkrishnar)
<table>
  <tr><th>Title</th><th>Link</th></tr>
  <!-- STACKOVERFLOW:START --><!-- STACKOVERFLOW:END -->
</table>

name: Latest YouTube Videos
on:
  schedule:
    # Runs every hour, on the hour
    - cron: "0 * * * *"
  workflow_dispatch:
permissions:
      contents: write

jobs:
  update-readme-with-youtube:
    name: Update this repo's README with latest videos from YouTube
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gautamkrishnar/blog-post-workflow@master
        with:
          feed_list: "https://www.youtube.com/feeds/videos.xml?channel_id=UCtvnB6R__6vdyjUEbDgAWHw"
          custom_tags: "channelId/yt:channelId/,videoId/yt:videoId/"
          date_format: "mmm d, yyyy"
          template: '<table><tr><td><a href="$url"><img width="140px" src="http://img.youtube.com/vi/$videoId/maxresdefault.jpg"></a></td>$newline<td><a href="$url">$title</a><br/>$date</td></tr></table>$newline'
          committer_email: "[email protected]"

name: Latest RadioGeek (Anchor)
on:
  schedule:
    # Runs “At 00:00 on Friday.”
    - cron: '0 0 * * FRI'
  workflow_dispatch:

jobs:
  update-readme-with-anchor:
    name: Update this repo's README with latest RadioGeek podcast feed from Anchor
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: gautamkrishnar/blog-post-workflow@master
        with:
          comment_tag_name: "RadioGeek-Anchor-feed"
          feed_list: "https://anchor.fm/s/6048890/podcast/rss"
          max_post_count: 1000
          commit_message: "🔥Update with lastest RadioGeek feed"
          committer_username: "🤖RadioGeek-Bot"
          committer_email: "<>"
          date_format: 'UTC: yyyy-mm-dd'
          template: "$newline #### - [$title]($url) $newline <details><summary>توضیحات</summary> $description </details> $newline <hr /> $newline"
          # Regex for remove HTML TAG:    /(<([^>]+)>)/ig
          item_exec: "post.description = post.description.replace('','')"
          disable_html_encoding: true

name: Latest blog post workflow
on:
  schedule:
    # Runs every hour, on the hour
    - cron: "0 * * * *"
  workflow_dispatch:
permissions:
      contents: write

jobs:
  update-readme-with-youtube:
    name: Update this repo's index.html with latest blog titles from blogspot
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gautamkrishnar/blog-post-workflow@v1
        with:
          readme_path: 'index.html'
          feed_list: "http://blog_name.blogspot.com/feeds/posts/default?alt=rss"
          template: '<li><a href="$url">$title</a></li>$newline'
          committer_email: "[email protected]"

• My own GitHub profile readme - YML File

• Error Code 128
• Looks like your website returned *XXX*, There is nothing blog post workflow can do to fix it. Please check your website's RSS feed generation source code. Also double check the URL.: This will happen if your website is blocking requests from the GitHub IP addresses. It can also happen if you give the workflow an invalid URL. First, check your URL. If it's working fine on your computer, then try debugging it using https://github.com/marketplace/actions/debugging-with-tmate establish an ssh connection with the Github runner and try to curl -I <URL> This will give you a 200 status code if your website is responding correctly. If its not responding with 200, you need to check your website's feed generation source code, you can also contact your hosting provider/DNS provider to know if they are blocking the GitHub public IP address. Some companies do that to prevent spam and DDOS attacks. As the message says there is nothing I can do to fix this issue, it needs to be sorted out with your hosting provider.

Please see the video by @codeSTACKr.

Please see CONTRIBUTING.md for getting started with the contribution.

Make sure that you follow CODE_OF_CONDUCT.md while contributing and engaging in the discussions.

When contributing, please first discuss the change you wish to make via an issue on this repository before making the actual change.

• Add more sources
• Fix bugs if any

If you are experiencing any bugs, don’t forget to open a new issue.

• All the 9K+✨ users of this workflow
• Everyone for making this project the top 20 most installed / starred action in the GitHub Marketplace
• @codeSTACKr for this amazing video
• CodeCov for this blog: Discovering the Most Popular and Most Used GitHub Actions
• the byte podcast
• JetBrains for sponsoring the Open Source License to my favorite IDE WebStorm:

• Thanks @github, for GitHub India Open Source Grants and for sponsoring me
• Thanks Tutanota for sponsoring free encrypted emails for my opensource projects:

Thanks goes to these wonderful people (emoji key):

Lucas Santos 💻 📖	Michael Currin 📖	WY 📖	Hussaina Begum 📖	Rigin Oommen 📖	Alberto Bonacina 📖	Vadorequest 📖
Jonah Lawrence 💻	Tim Myers 📖	Kaustubh Gupta 📖	Mathieu Ledru 📖	Aditya Dharmawan Saputra 📖	Minji 📖	Dhanushka Madushan 📖
Curtis Timson 💻	Md Obydullah 📖	David Aparicio 📖	Yudu 📖	Changhun Lee 📖	Adrián Paniagua 📖	Mukto Akash 📖

This project follows the all-contributors specification. Contributions of any kind welcome!

Hope you liked this project, don't forget to give it a star ⭐.