You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is `gpg` program available, Elegant Git will try to configure
signing for the Git objects during execution of `acquire-repository`
command.
Now `read` addon supports values with spaces also.
#11
Copy file name to clipboardexpand all lines: docs/configuration.md
+14
Original file line number
Diff line number
Diff line change
@@ -52,3 +52,17 @@ significantly improve user experience.
52
52
53
53
The configuration is a call of `git config "alias.<command>" "elegant <command>"` (`i`) for each Elegant
54
54
Git command.
55
+
56
+
# Signature
57
+
This configuration aims to say Git how to sign commits, tags, and other objects you create. It starts after
58
+
all other configurations. In the beginning, all available signing keys will be shown. Then, you need to choose
59
+
the key that will be used to make signatures. If the key is provided, the configuration triggers, otherwise,
60
+
it does not apply. The signing configuration consists of
61
+
62
+
1. setting `user.signingkey` (`l`) to a provided value
63
+
2. setting `gpg.program` (`l`) to a full path of `gpg` program
64
+
3. setting `commit.gpgsign` (`l`) to `true`
65
+
4. setting `tag.forceSignAnnotated` (`l`) to `true`
66
+
5. setting `tag.gpgSign` (`l`) to `true`
67
+
68
+
For now, only `gpg` is supported. If you need other tools, please [create a new feature request](https://github.com/bees-hive/elegant-git/issues/new/choose).
0 commit comments