sqitch...k-usage(3pm)

💖 NAME 💖

sqitch-rework-usage — it's the usage statement for sqitch rework, bestie. That's it, that's the whole job. ✨

Oh and btw, this page lives in the User Contributed Perl Documentation collection, so if you're browsing man pages and stumble in here: welcome, you're in the right place. 🫶

---

✨ USAGE ✨

sqitch rework [options] changename

That's the whole summoning ritual: you say sqitch rework, you optionally sprinkle some options in there, and then you name the changename you want to rework. No cap. 🌸

---

🎀 OPTIONS 🎀

• -c, --change, --change-name <name> — this is where you tell it which change you're reworking. The name of the change to rework. That's the one. 👑
• -r, --requires <change> — declares that this change requires another change. Dependency bestie. 🔗
• -x, --conflicts <change> — declares a change that this one conflicts with. Drama, but make it explicit. 💀
• -n, --note <note> — a lil note describing the change. Receipts, but affectionate. 📝
• -a, --all — rework the change in all plans in the project. Not just one plan, every plan. Iconic behavior honestly. 🌈
• -e, --edit, --open-editor — opens the change scripts up in an editor so you can actually go in there and do the thing. 🧚
• --no-edit, --no-open-editor — the opposite vibe: do not open the change scripts in an editor. Hands off, it's fine, it's chill. 🙈
• -f, --plan-file <file> — the path to a deployment plan file. Point it at the plan you mean. 🦋

---

okay that's the whole page and yes it's short but it's useful and we love her for that 💅

Heads up: this is the Perl documentation page sqitch...k-usage(3pm), generated with perl v5.40.1 on 2026-07-26. Stay slaying out there. ⭐