Commit staged changes in a project's dev clone
POST/api/commit_project_git/:guid
Commits staged changes in the current user's dev clone of the project using the supplied commit message, and emits a script-commit system event. Returns 400 if there is nothing staged or the message is blank, 404 if the project doesn't exist, and 502 if the underlying git commit fails for another reason.
When both workflow_guid and node_guid are given, the commit is
confined to that node and the libraries it links to - the scope the
Scripting page's Source Control tab shows. Anything staged outside it is
unstaged rather than committed, so work staged from another node can't
ride along in a commit made from here; its working-tree changes survive
untouched (see commit_with_message).
Request
Responses
- 200
- 400
- 404
- 422
- 502
Successful Response
Nothing to commit, message missing, or invalid path segment
Project not found
Validation Error
git commit failed