How to Add Your Latest Tweets to Your GitHub Profile README

Embedding tweets in a GitHub README updates a designated section with your recent posts from Twitter/X. Like the blog post workflow, it uses a GitHub Action on a daily schedule to fetch your latest content and commit the updated list to your README.

Note: Twitter/X has significantly restricted its public API since 2023. Direct API access now requires a paid developer plan. The most practical workarounds use third-party RSS services that bridge Twitter content to an RSS feed format — allowing the blog-post-workflow Action to fetch your tweets without direct API access. Nitter instances (when available) and RSS.app are common bridges.

Using an RSS bridge service:

1. Create a Twitter RSS feed URL using a service like RSS.app, rsshub.app, or similar. For rsshub: https://rsshub.app/twitter/user/YOUR_TWITTER_USERNAME.
2. Add comment markers to your README:

## Recent Tweets
<!-- TWITTER:START -->
<!-- TWITTER:END -->

3. Create .github/workflows/twitter.yml:

name: Latest Twitter Posts
on:
  schedule:
    - cron: '0 0 * * *'
  workflow_dispatch:
permissions:
  contents: write
jobs:
  update-readme:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: gautamkrishnar/blog-post-workflow@v1
        with:
          feed_list: "https://rsshub.app/twitter/user/YOUR_TWITTER_USERNAME"
          comment_tag_name: TWITTER
          max_post_count: 3
          template: "- $title ($date)"

Replace YOUR_TWITTER_USERNAME with your actual Twitter/X handle.

Given Twitter/X API restrictions and the unreliability of RSS bridges (which can be rate-limited or go offline), many developers choose to link to their Twitter profile rather than embed tweets. This is often the more reliable option:

[![Twitter](https://img.shields.io/badge/Twitter-1DA1F2?style=for-the-badge&logo=twitter&logoColor=white)](https://twitter.com/YOUR_USERNAME)

Or with your follower count as social proof, using the shields.io dynamic badge:

![Twitter Follow](https://img.shields.io/twitter/follow/YOUR_USERNAME?style=social)

For developers active on multiple platforms, a row of social badges (Twitter, LinkedIn, YouTube, Dev.to) is often more effective than trying to embed recent content from any single platform.

If the RSS bridge URL returns empty results, the bridge service may be rate-limited or blocking your account. Try an alternative RSS service or test the feed URL directly in an RSS reader to verify it is returning content.

If the workflow runs but the comment markers are not updated, verify that comment_tag_name: TWITTER matches the markers in your README exactly. The tag name (between <!-- and :START -->) must match the YAML value precisely.

Due to the evolving nature of Twitter/X's API policies, any embedded tweet approach may require maintenance over time as bridge services respond to policy changes. The static badge linking approach requires no maintenance and is more long-term reliable.