#mergify
Live, measured metrics for the hashtag #mergify from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mergify
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-29 16:46 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-29 16:46 UTCNo related tags with measured usage found for #mergify.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:46 UTCEverything below is measured over the latest 6 public posts (spanning ~48194 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.3
Top of the latest posts
🚀 An epic saga of merge queues, where we heroically trace the riveting #evolution from #Bors to #Mergify, with all the drama of a lukewarm #GitHub release note. 🙄 Apparently, knowing the origin story of this "exciting" #CI/CD feature will
The Origin Story of Merge Queues https://mergify.com/blog/the-origin-story-of-merge-queues #HackerNews #OriginStory #MergeQueues #Mergify #TechInnovation #SoftwareDevelopment
Why #mergify if there's #bors ?
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/mergify