#pullrequests

Live, measured metrics for the hashtag #pullrequests from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #pullrequests

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.

$5.00/ year · 12-character #name
Claim #pullrequests — $5.00/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
1
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0
Avg reactions / post
Mastodon · last 40
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-09-29 17:07 UTC
0
09-23
0
09-24
1
09-25
0
09-26
0
09-27
0
09-28
0
09-29

1 uses by 1 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-09-29 17:07 UTC
#pullrequestsrules
0 uses · 0 accounts / 7d
#pullrequestswelcome
0 uses · 0 accounts / 7d
#pullrequestsniping
0 uses · 0 accounts / 7d
#24pullrequests
0 uses · 0 accounts / 7d
#pullrequestsarewelcome
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-29 17:07 UTC

Everything below is measured over the latest 40 public posts (spanning ~8918 hours).

Posting hours (UTC) — busiest: 03:00

00:0012:0023:00

Languages: English (38) · German (1) · Portuguese (1)

Avg boosts / post: 0.3

Top of the latest posts

  • Greptile (@greptile) Greptile이 NVIDIA의 크고 복잡한 코드베이스에서 39만 5,000건 이상의 PR을 검토했다고 밝혔다. 한 팀에서는 PR 병합까지 평균 시간이 24시간 이상에서 6시간으로 단축됐으며, AI 코드 리뷰 도구가 엔지니어의 리뷰 병목을 줄일 수 있음을 보여주는 운영 사례다. https://x.com/greptile/status/2103140056256888894 #ai #coderevi

    ainews@[email protected]♥ 0↻ 12026-09-25 01:57 UTCView post →

  • So on a day when my #company issued #laptop and #GitHub conspired to severely reduce my #throughput, I still managed to open 14 #pullrequests. Small ones but they actually exist. As reward, in the hopes that this problem is related to #DNS,

    TSM at Work@[email protected]♥ 0↻ 02026-09-03 03:04 UTCView post →

  • I don't know if it's a good thing or a bad thing that this current family of stories I'm working on turned into a network of 38 coordinated #pullrequests, the last 6 being hopefully #disposable. I guess it's nifty that this #project is plan

    TSM at Work@[email protected]♥ 0↻ 02026-08-15 01:04 UTCView post →

#pullrequests across platforms

every network with a public tag surface

Follow #pullrequests straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/pullrequests