git_commit
Directly commit the given file with the given message
| git_commit | |
|---|---|
| Supported platforms | ios, android, mac |
| Author | @KrauseFx |
4 Examples
git_commit(path: "./version.txt", message: "Version Bump")
git_commit(path: ["./version.txt", "./changelog.txt"], message: "Version Bump")
git_commit(path: ["./*.txt", "./*.md"], message: "Update documentation")
git_commit(path: ["./*.txt", "./*.md"], message: "Update documentation", skip_git_hooks: true)
Parameters
| Key | Description | Default |
|---|---|---|
path |
The file(s) or directory(ies) you want to commit. You can pass an array of multiple file-paths or fileglobs "*.txt" to commit all matching files. The files already staged but not specified and untracked files won't be committed | |
message |
The commit message that should be used | |
skip_git_hooks |
Set to true to pass --no-verify to git |
false |
allow_nothing_to_commit |
Set to true to allow commit without any git changes in the files you want to commit | false |
* = default value is dependent on the user's system
Documentation
To show the documentation in your terminal, run
fastlane action git_commit
CLI
It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal
fastlane run git_commit
To pass parameters, make use of the : symbol, for example
fastlane run git_commit parameter1:"value1" parameter2:"value2"
It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:"1,2,3"). Hashes are not currently supported.
It is recommended to add all fastlane actions you use to your Fastfile.
Source code
This action, just like the rest of fastlane, is fully open source, view the source code on GitHub