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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+22-21Lines changed: 22 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ Please include a short and precise description about what you have done in the c
14
14
15
15
We strongly recommend use GPG to sign your commit, and add a sign-off message after your commit message. We enabled vigilant mode so we can make sure that all commits are committed by yourself.
16
16
17
-
```
18
-
$ git commit -s -S -m "what-i-have-done"
17
+
```bash
18
+
git commit -s -S -m "what-i-have-done"
19
19
```
20
20
21
21
For now we don't force contributors to sign their commits, but in the future we might refuse Pull Requests that commits are not signed.
@@ -25,7 +25,8 @@ For now we don't force contributors to sign their commits, but in the future we
25
25
1. We indent using Tab, you can choose any tab size you want when you browsing or writing code, but always choose Tab for indent;
26
26
27
27
2. All Go source files must add an Apache 2.0 license header comment, you can add your name and email under `Contributors` section like this:
@@ -37,7 +38,7 @@ Licensed under the Apache License, Version 2.0 (the "License");
37
38
you may not use this file except in compliance with the License.
38
39
You may obtain a copy of the License at
39
40
40
-
http://www.apache.org/licenses/LICENSE-2.0
41
+
http://www.apache.org/licenses/LICENSE-2.0
41
42
42
43
Unless required by applicable law or agreed to in writing, software
43
44
distributed under the License is distributed on an "AS IS" BASIS,
@@ -59,43 +60,43 @@ limitations under the License.
59
60
60
61
3. How to generate or use your existing GPG key:
61
62
62
-
-[Generating a new GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key)
63
-
64
-
-[Checking for existing GPG keys](https://docs.github.com/en/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys)
63
+
-[Generating a new GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key)
64
+
65
+
-[Checking for existing GPG keys](https://docs.github.com/en/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys)
65
66
66
-
-[Adding a GPG key to your GitHub account](https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account)
67
+
-[Adding a GPG key to your GitHub account](https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account)
67
68
68
-
-[Telling Git about your signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key)
69
+
-[Telling Git about your signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key)
As RFC2136 is actually a standard, not a DNS provider, we can only provide IETF documentation about this: https://datatracker.ietf.org/doc/html/rfc2136
102
+
As RFC2136 is actually a standard, not a DNS provider, we can only provide IETF documentation about this: <https://datatracker.ietf.org/doc/html/rfc2136>
- When using AliCloud DNS provider, you may encounter the following error: "You can’t finish this operation because the last operation has not been finished". You can try to wait for next DNS update and its not always reproducible.
0 commit comments