FAQ

🚀Frequently Asked Questions

Support Guide

Find answers about commit scope, pushing, Run equivalence, empty commits, changelog generation, and staging.

Commandcusty commit

📦Category

Git Operations

🚀Quick Command

custy commit [OPTIONS]

---

FAQGit commitsupport

---

Overview

These answers clarify how Custy's commit profile differs from a standalone Git commit and where its side effects stop.

ℹ️A multi-stage profile

custy commit prepares project artifacts before it reaches the final Git commit stage.

---

Is `custy commit` Equivalent to `git commit`?

No. Custy runs a preparation and release-artifact pipeline before its final Git commit stage.

---

Does It Push the Commit?

No. Use custy push after review, or choose a public profile that intentionally includes pushing.

---

How Does `custy run commit` Differ?

Both forms select the registered commit profile. The direct command exposes commit-specific CLI overrides, while the generic Run command accepts profile selection and global execution context.

---

Can It Create an Empty Commit?

Yes, when --allow-empty-commit or the corresponding resolved configuration is enabled. Use it only when empty history is intentional.

---

Does It Generate the Changelog?

Yes. Changelog generation is part of the registered commit profile before backup, staging, and commit creation.

---

Should I Stage Manually First?

You can, but review the resolved stage mode because the profile also contains a staging step. Use manual or none behavior when you need to preserve an exact pre-staged selection.