merge-pr
Skill5k starsChanged 9 days agoMITView on GitHub
Merge one or more pagy pull requests the way the maintainer wants (base branch, squash subject with the 💎 prefix, empty body, local branches updated). Use when asked to merge, land or handle a PR.
- Deletes or force-pushes
- Commits and pushes
18 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- kratocz/skillstheir own version, first seen Nov 15, 2026
- kdy1/kdy1-scriptstheir own version, first seen Nov 15, 2026
- developerz-ai/open-mmorpgtheir own version, first seen Nov 10, 2026
- mihai-dinculescu/tapotheir own version, first seen Nov 9, 2026
- ShareX/ShareXtheir own version, first seen Nov 8, 2026
- r3bl-org/r3bl-open-coretheir own version, first seen Oct 17, 2026
Who's talking about ddnexus/pagy
- luckyframework/lucky“Add Lucky::Paginator”GitHub · Mar 3, 2020 · 7 reactions
- @sulmanweb.com“8/10 Pagy github.com/ddnexus/pagy #20DayGemChallenge #RubyOnRails #distilled.rb”Bluesky · Dec 14, 2024 · 4 likes
- among-use/among-use“[ADD]userの一覧ページを作成”GitHub · Jul 29, 2021 · 3 reactions
- A Hacker News story“Pagy: Best Pagination Ruby Gem”Hacker News · Jan 26, 2026 · 2 points
- @jvrc.ca“Choose 20 Ruby gems that you've used time and time again, or have inspired you in some way. One gem per day …”Bluesky · Dec 23, 2024 · 2 likes
The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 55
Talked about on GitHub, Hacker News and Bluesky (55 times).
On GitHub · 50
- Mar 3, 2020Add Lucky::Paginator — luckyframework/lucky7 reactions · 5 comments
- Jul 29, 2021[ADD]userの一覧ページを作成 — among-use/among-use3 reactions · 2 comments
- May 25, 2018Move pagination to `pagy` — decidim/decidim2 reactions · 3 comments
- Oct 15, 2026expose limit and offset via public method — basecamp/rails-active_search1 reaction
- Aug 3, 2026build(deps): bump the ruby-dependencies group across 1 directory with 10 updates — Shimizu-Technology/HafaPass1 reaction · 2 comments
45 more on GitHub
- Jul 20, 2026build(deps): bump the ruby-dependencies group across 1 directory with 9 updates — Shimizu-Technology/HafaPass1 reaction · 2 comments
- May 24, 2026chore(deps): bump pagy from 43.5.4 to 43.5.5 — unclesp1d3r/CipherSwarm1 reaction · 2 comments
- Apr 19, 2026chore(deps): bump pagy from 43.5.0 to 43.5.1 — unclesp1d3r/CipherSwarm1 reaction · 2 comments
- Mar 29, 2026chore(deps): Bump pagy from 43.3.1 to 43.4.4 — dpaola2/show-notes1 reaction
- Mar 24, 2026Use Pagy’s new options API — davidcelis/api-pagination1 reaction · 1 comment
- Mar 22, 2026chore(deps): Bump pagy from 43.3.1 to 43.4.2 — dpaola2/show-notes1 reaction · 1 comment
- Mar 15, 2026chore(deps): Bump pagy from 43.3.1 to 43.3.3 — dpaola2/show-notes1 reaction · 1 comment
- Mar 1, 2026chore(deps): Bump pagy from 43.2.9 to 43.3.1 — dpaola2/show-notes1 reaction
- Feb 22, 2026chore(deps): Bump pagy from 43.2.9 to 43.3.0 — dpaola2/show-notes1 reaction · 1 comment
- Dec 19, 2025chore(deps): bump pagy from 43.2.1 to 43.2.2 — hackclub/flavortown1 reaction · 1 comment
- Dec 18, 2025Bump pagy from 43.2.0 to 43.2.2 — hackclub/hackatime1 reaction · 1 comment
- Dec 15, 2025Bump pagy from 43.2.0 to 43.2.1 — hackclub/hackatime1 reaction · 1 comment
- Dec 15, 2025chore(deps): bump pagy from 43.2.0 to 43.2.1 — hackclub/flavortown1 reaction
- Dec 4, 2025Bump pagy from 43.1.8 to 43.2.0 — hackclub/hackatime1 reaction
- Dec 4, 2025chore(deps): bump pagy from 43.1.8 to 43.2.0 — hackclub/flavortown1 reaction
- Dec 1, 2025chore(deps): bump pagy from 43.1.6 to 43.1.8 — hackclub/flavortown1 reaction
- Nov 28, 2025Bump pagy from 43.1.4 to 43.1.8 — hackclub/hackatime1 reaction
- Nov 27, 2025Bump pagy from 43.1.4 to 43.1.6 — hackclub/hackatime1 reaction · 1 comment
- Nov 27, 2025chore(deps): bump pagy from 43.1.5 to 43.1.6 — hackclub/flavortown1 reaction
- Nov 26, 2025Bump pagy from 43.1.4 to 43.1.5 — hackclub/hackatime1 reaction · 1 comment
- Nov 24, 2025Bump pagy from 43.1.1 to 43.1.4 — hackclub/hackatime1 reaction
- Nov 21, 2025Bump pagy from 43.1.0 to 43.1.1 — hackclub/hackatime1 reaction
- Nov 20, 2025Bump pagy from 43.0.6 to 43.1.0 — hackclub/hackatime1 reaction
- Nov 19, 2025Bump pagy from 43.0.6 to 43.0.7 — hackclub/hackatime1 reaction · 1 comment
- Nov 11, 2025Bump pagy from 9.4.0 to 43.0.4 — opf/openproject1 reaction · 2 comments
- Oct 9, 2024Array params are lost when constructing URLs — josefarias/hotwire_combobox1 reaction · 1 comment
- May 21, 2021Replace Kaminari with Pagy for pagination — openfoodfoundation/openfoodnetwork1 reaction
- Aug 18, 2020initial pagy install for tag page pagination, to solve will_paginate issues — publiclab/plots21 reaction · 10 comments
- Jun 6, 2019Benchmarking against Pagy vs Will_Paginate — kaminari/kaminarisays it tested it1 reaction · 3 comments
- Nov 9, 2026chore(deps): Bump pagy from 43.5.6 to 43.8.1 — NewtonMutugi/arc-ticketing-system0 reactions
- Nov 8, 2026Bump pagy from 9.4.0 to 43.4.4 — Writtek07/swastik-webapp0 reactions
- Nov 7, 2026Bump pagy from 43.7.0 to 43.8.1 — khasinski/tabdevs.pl0 reactions
- Nov 6, 2026build(deps): bump pagy from 9.4.0 to 43.8.1 — isaacm/casa0 reactions
- Nov 5, 2026Bump pagy from 43.6.2 to 43.8.1 — maimux2x/yondayo0 reactions
- Nov 3, 2026Bump pagy from 43.6.1 to 43.8.1 — MattGLut/coco_stained_glass_marketing0 reactions
- Oct 28, 2026Bump pagy from 43.6.3 to 43.8.1 — Menocas17/fsy_management0 reactions · 2 comments
- Oct 27, 2026Bump pagy from 43.7.1 to 43.8.1 — seocahill/meitheal0 reactions
- Oct 27, 2026build(deps): Bump pagy from 43.6.2 to 43.8.1 — TheRPGClub/TheRPGClub-api0 reactions
- Oct 26, 2026build(deps): bump pagy from 43.7.0 to 43.8.1 — senseiseo/online_shop0 reactions
- Oct 26, 2026Bump pagy from 43.7.0 to 43.8.1 — abdellrahmanHq/book_app0 reactions
- Oct 26, 2026chore(deps): bump pagy from 43.7.0 to 43.8.1 — omni395/travel_fi0 reactions
- Oct 25, 2026Build(deps): Bump pagy from 43.7.1 to 43.8.1 — tripledub/tessera-merchant-hub0 reactions
- Oct 25, 2026Bump pagy from 43.7.0 to 43.8.1 — Muhxmd/BlogApp0 reactions
- Oct 24, 2026chore(deps): bump pagy from 43.6.1 to 43.8.1 — ar1vit0r/rails-marketplace0 reactions
- Oct 22, 2026Chore(deps): Bump pagy from 43.7.0 to 43.8.1 — chucoyos/campos0 reactions
On Hacker News · 3
- Jan 26, 2026Pagy: Best Pagination Ruby Gem2 points
- Jul 30, 2018The ultimate pagination ruby gem2 points
- May 24, 2018Pagy – The ultimate pagination ruby gem1 point
On Bluesky · 2
- Dec 14, 20248/10 Pagy github.com/ddnexus/pagy #20DayGemChallenge #RubyOnRails #distilled.rb — @sulmanweb.com4 likes and reposts
- Dec 23, 2024Choose 20 Ruby gems that you've used time and time again, or have inspired you in some way. One gem per day for 20 days, in no particular… — @jvrc.ca2 likes and reposts
Used with
Projects with it also use implement-issue, create-pr and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillimplement-issue
Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 7 projects that use this
sahinSkillcreate-issue
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- ShareX/ShareX★ 41ksame name
- cube-js/cube★ 21ksame name
- mihai-dinculescu/tapo★ 877same name
- bazel-contrib/rules_python★ 695same name
- kkokosa/dotLLM★ 528same name
- r3bl-org/r3bl-open-core★ 486same name
- tbhb/vale-ai-tells★ 118same name
- TermiX-official/cryptoclaw★ 100same name
- kdy1/kdy1-scripts★ 34same name
- neul-labs/openclawMU★ 33same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
Always squash-merge. The subject is the PR title followed by (#N), which is what GitHub proposes.
- Very specific: line 65
After a merge on master, dev must follow: fast-forward local dev on the new master and push it.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Merging a pull request
This is the procedure for merging a PR in pagy. Run it only when asked to merge: checking a PR never implies merging it. When several PRs are open, process them from the oldest to the newest.
Where a PR lands
A PR from a GitHub bot (dependabot, workflow bumps) stays on master and is merged there.
A PR from a user lands on dev, never on master: change its base first.
gh pr edit N --base devmaster may receive directly only what keeps the code identical to the published gem: docs
fixes, workflows, scripts, tests and other chores. Any change under gem/ goes on dev.
Before merging
The PR must be rebased on the tip of its base branch and its checks must be green. For a bot
PR that is behind, comment @dependabot rebase. For a user PR that is behind, rebase locally
and push to the fork; --force-with-lease to a bare URL fails, so add the fork as a remote
first or use plain --force.
git fetch origin pull/N/head:pr-N
git rebase dev pr-N
git remote add <user> https://github.com/<user>/pagy.git && git fetch <user>
git push --force-with-lease <user> pr-N:<branch>The squash commit
Always squash-merge. The subject is the PR title followed by (#N), which is what GitHub
proposes. When the PR touches any file under gem/, prepend 💎 to the subject: the release
script builds the CHANGELOG from the 💎 commits and warns about unmarked gem commits. Add
(Fix #issue) when the PR closes an issue. The body is always empty.
gh pr merge N --squash --subject "💎 <PR title> (#N)" --body ""Since the body is empty, GitHub does not close the issue linked in the PR body: check it and close it by hand.
gh issue close N --comment "Fixed by #PR, merged on dev; it will be in the next release."After merging
Fast-forward the local branch that received the merge and delete the temporary branch.
git pull --ff-only origin dev # or master for a bot PR
git branch -D pr-NAfter a merge on master, dev must follow: fast-forward local dev on the new master and
push it. If dev has its own commits, rebase them on master and push with
--force-with-lease. origin/dev is never left behind master.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

