' ( man) but then using ' git maintenance unregister' ( man) to remove the config option. The current implementation instead segfaults.Ī user could run into this issue if they used ' git maintenance start' ( man) to initialize their cron schedule using ' git for-each-repo -config=maintenance.repo. ' git for-each-repo -config=X' ( man) should return success without calling any subcommands when the config key ' X' has no value. (Merged by Junio C Hamano - gitster - in commit aa08688, ) for-each-repo: do nothing on empty config See commit 6c62f01 () by Derrick Stolee ( derrickstolee). With Git 2.30.1 (Q1 2021), " git for-each-repo -config= " ( man) should not run for any repository when the configuration variable is not defined even once.
#TERMINAL GIT LIST BRANCHES CODE#
Then the git for-each-repo process returns that exit code without runningĮach git -C subprocess inherits the standard file If any git -C subprocess returns a non-zero exit code, Git repository, then only the system and global config is used. If git for-each-repo is run in a directory that is not a These config values are loaded from system, global, and local Git config,Īs available. Use the given config variable as a multi-valued list storingĪbsolute path names. In the multi-valued config variable maintenance.repo. This will run git -C maintenance run for each value Git for-each-repo -config=maintenance.repo maintenance run Stored in a maintenance.repo config variable using THE BEHAVIOR MAY CHANGE.įor example, we could run maintenance on each of a list of repositories Known options or - indicator are used as the arguments for the Git Run a Git command on a list of repositories. Redirect the result in a file 'list-repos.txt', then register those repositories, reading each line of the file: while IFS="" read -r repo || [ -n "$
#TERMINAL GIT LIST BRANCHES HOW TO#
If you can come up with how to show branch name and repo's status
0 kommentar(er)
