- CONFIGURATION AND ENVIRONMENT
- BUGS AND LIMITATIONS
- LICENSE AND COPYRIGHT
git-files - Get information on files changed across branches.
This documentation refers to git-files version 1.1.9
git-files [changed] [(-s|--age) days] [(-s|--since) YYYY-MM-DD] [-v|--verbose] git-files local [(-s|--age) days] [(-s|--since) YYYY-MM-DD] [-v|--verbose] git-files set [-v|--verbose] git-files SUB COMMANDS: changed Files that have changed local See if any locally (to the branch) modified files have been modified in other branches. set Sets files modified time to the date they were last committed. OPTIONS: -a --age[=]days Age in days to look changed files -s --since[=]YYYY-MM-DDTHH::MM Files changed since date -t --tag[=]tag Tag to use to define a release -b --branch[=]branch Branch to use to define a release -l --local Use master as release -m --max-history[=]int Limit getting release history to this number of commits -v --verbose Show more detailed option --version Prints the version information --help Prints this help information --man Prints the full documentation for git-files
git-files command helps to find out which files are being actively changed by whom and where those files changes are occurring. The aim is to help developers see if other developers are working on the same files. This should reduce the potential for conflicts later on (or at least start the process to resolve those conflicts).
Executes the git workflow command
There are no known bugs in this module.
Please report problems to Ivan Wills (email@example.com).
Patches are welcome.
Ivan Wills - (firstname.lastname@example.org)
Copyright (c) 2014 Ivan Wills (14 Mullion Close, Hornsby Heights, NSW Australia 2077). All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.