- Git Version Control Cookbook
- Aske Olsson Rasmus Voss
- 359字
- 2021-12-08 12:33:50
Querying the existing configuration
In this example, we will look at how we can query the existing configuration and set the configuration values.
Getting ready
We'll use jgit
again by using the following command:
$ cd jgit
How to do it...
To view all the effective configurations for the current Git repository, run the following command:
$ git config --list user.name=Aske Olsson user.email=askeolsson@switch-gears.dk core.repositoryformatversion=0 core.filemode=false core.bare=false core.logallrefupdates=true remote.origin.url=https://git.eclipse.org/r/jgit/jgit remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master
The previous output will of course reflect the user running the command. Instead of Aske Olsson
as the name and the e-mail, the output should reflect your settings.
If we are just interested in a single configuration item, we can just query it by its section.key
or section.subsection.key
:
$ git config user.name Aske Olsson $ git config remote.origin.url https://git.eclipse.org/r/jgit/jgit
How it works...
Git's configuration is stored in plaintext files, and works like a key-value storage. You can set/query by key and get the value back. An example of the text-based configuration file is shown as follows (from the jgit
repository):
$ cat .git/config [core] repositoryformatversion = 0 filemode = false bare = false logallrefupdates = true [remote "origin"] url = https://git.eclipse.org/r/jgit/jgit fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master
There's more...
It is also easy to set configuration values. Just use the same syntax as you did when querying the configuration, except you need to add an argument to the value. To set a new e-mail address on the LOCAL
layer, we can execute the following command line:
git config user.email askeolsson@example.com
The LOCAL
layer is the default if nothing else is specified. If you require whitespaces in the value, you can enclose the string in quotation marks, as you would do when configuring your name:
git config user.name "Aske Olsson"
You can even set your own configuration, which does not have any effect on the core Git, but can be useful for scripting/builds and so on:
$ git config my.own.config "Whatever I need"
List the value
$ git config my.own.config Whatever I need
It is also very easy to delete/unset configuration entries:
$ git config --unset my.own.config
List the value
$ git config my.own.config
- HTML5+CSS3王者歸來
- MySQL數(shù)據(jù)庫應(yīng)用與管理 第2版
- MySQL 8 DBA基礎(chǔ)教程
- Java 9模塊化開發(fā):核心原則與實踐
- Mastering Drupal 8 Views
- Microsoft Dynamics AX 2012 R3 Financial Management
- 現(xiàn)代C++編程實戰(zhàn):132個核心技巧示例(原書第2版)
- Instant PHP Web Scraping
- IoT Projects with Bluetooth Low Energy
- Django Design Patterns and Best Practices
- PostgreSQL Developer's Guide
- Microsoft Exchange Server 2016 PowerShell Cookbook(Fourth Edition)
- Mastering Object:Oriented Python(Second Edition)
- Learning D3.js 5 Mapping(Second Edition)
- 程序員的英語