#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.
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.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 11:57 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-27 11:57 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:57 UTCEverything below is measured over the latest 40 public posts (spanning ~9539 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (39) · Portuguese (1)
Avg boosts / post: 0.3
Top of the latest posts
"Stacked PRs" is a proxy signal for failed engineering culture. What you are saying is that you either can't/won't make a PR of reviewable size or that your team is incapable of getting reviewable PR's merged in a timely manner, and instead
Just published two new #greasemonkey scripts to scratch a long-standing itch. When working with #pullrequests on #Github, I like cleanly separated small commits. I then review commit-by-commit, but github does not show on comments what comm
Microsoft product manager Leah Tran focuses on a new (18.7) feature of Visual Studio that allows developers to do a number of things with pull requests, review features in particular. This expands on the ide's capacity to handle source cont
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