sqitch...s-usage(3pm)

✨ NAME ✨

okay so this is the sqitch-status-usage page — it's the Sqitch status usage statement, and it lives in the User Contributed Perl Documentation as sqitch...s-usage(3pm). Bestie, it's literally the vibe check for how you run sqitch status. 💖

---

🦋 USAGE 🦋

Here's the whole shape of it, no cap:

sqitch status [options] [<database>]

That's it. That's the move. ✨

---

💅 OPTIONS 💅

Every single flag, and yes, we're listing all of them because we don't skip. 🫶

• -t, --target <target> — the database to which to connect. That's the target, babes.
• --project <project> — the project for which to retrieve the status. Tell it which project you're checking on.
• --show-changes — include a list of deployed changes. More tea, please. 🍵
• --show-tags — include a list of applied tags. Tags stay iconic.
• --date-format <format> — display dates using the specified format. You pick the format, it shows the dates that way.
• --registry <registry> — registry schema or database. That's the registry situation.
• --db-client <path> — path to the engine command-line client. Point it at the client, bestie.
• -d, --db-name <name> — database name. Name the database.
• -u, --db-user <user> — database user name. Who are you logging in as? That.
• -h, --db-host <host> — database server host name. Where's the server at? That.
• -p, --db-port <port> — database server port number. The port, obviously. 🔌
• -f, --plan-file <file> — path to a deployment plan file. The plan file, right there.

---

So yeah, that's the whole usage statement. This page is from the User Contributed Perl Documentation, it's sqitch...s-usage(3pm) again, and the footer energy is perl v5.40.1, dated 2026-07-26. Bye bestie, go check your status. 💅✨