vcs: Restructure vcs module

Just like writing and qutebrowser modules, restructured the version
control software module to make more use of dotter's ability to
precisely link files. All contained programs have a top-level directory
and all the files that correspond to that specific software lie beneath
in the directory tree.
This commit is contained in:
Marty Oehme 2024-09-18 17:38:44 +02:00
parent 0b6f0c235d
commit bcd93eb237
Signed by: Marty
GPG key ID: EDBF2ED917B2EF6A
8 changed files with 9 additions and 3 deletions

View file

@ -15,6 +15,10 @@ sh = "~"
[vcs.files] [vcs.files]
"vcs/README.md" = { target = "~/NOWHERE", type = "symbolic", if = "false" } "vcs/README.md" = { target = "~/NOWHERE", type = "symbolic", if = "false" }
"vcs/git" = "~/.config"
"vcs/jj" = "~/.config/jj"
"vcs/gitignore/config" = "~/.config"
"vcs/gitignore/local" = "~/.local"
vcs = "~" vcs = "~"
[nvim.files] [nvim.files]

View file

@ -1,15 +1,17 @@
# Git module # Version control software module
[git](https://git-scm.com/) - a distributed version control system [git](https://git-scm.com/) - a distributed version control system
[jujutsu](https://martinvonz.github.io/jj/latest/) - a change-based version control system
## What's in this module ## What's in this module
[[_TOC_]] [[_TOC_]]
## Global git settings ## Global vcs settings
This is probably the first thing that needs to be customized, since it points to a different identity for each git user. This are probably the first things that need to be customized, since it points to a different identity for each git user.
I sign all my commits by default, so take out the corresponding lines if you don't, or exchange it with your gpg key. I sign all my commits by default, so take out the corresponding lines if you don't, or exchange it with your gpg key.
Similarly for jujutsu, change the identity and remove the lines concerning gpg signing if you don't use it.
Git will rewrite any remotes using http(s) to use the ssh notation for pushes to github and gitlab so that, even if you set up the repository using an https url you can utilize your usual ssh key for pushing. Git will rewrite any remotes using http(s) to use the ssh notation for pushes to github and gitlab so that, even if you set up the repository using an https url you can utilize your usual ssh key for pushing.