A built-in commit command with a strict git workflow exists but is off unless a server enables it.
A commit slash command with fixed git rules and limited tool access is compiled in with its gate set false.
What's wrong with this entry?
A command named "commit" is registered that gathers git status, the diff against HEAD, the branch and the last 10 commits, then follows a fixed workflow: never amend after a failed pre-commit hook, never use --no-verify, prefer naming files over git add -A, and never push unless asked. Its tool access is limited to git add, status and commit. It appears only when the tengu_cinder_relay gate resolves true; the value compiled into the build is false, so whether it shows up is decided by server config.
- It is separate from the existing commit-push-PR flow.
Create a git commit. Use whenever you are about to create a commit, tengu_cinder_relay
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command