StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-12-16 21:58:50 +08:00
Code Issues Projects Releases Packages Wiki Activity

DOCS: Fixed the incorrect inline anchors links (#2132)

Browse source 
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
This commit is contained in:
Jeffrey Cafferata 2023-03-11 14:53:37 +01:00 • committed by GitHub
parent 2d241b7a78
commit c80f8a606b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
documentation/opinions.md
View file

@ -73,7 +73,7 @@ the DNS names are downcased.
This reduces code complexity, reduces the number of edge-cases that must This reduces code complexity, reduces the number of edge-cases that must
be tested, and makes the system safer to operate. be tested, and makes the system safer to operate.
Yes, we know that DNS is case insensitive. See [Opinion #3](#opinion-3--dnsconfigjs-are-not-zonefiles). Yes, we know that DNS is case insensitive. See [Opinion #3](#opinion-3-dnsconfig.js-are-not-zonefiles).
# Opinion #5: Users should state what they want, and DNSControl should do the rest # Opinion #5: Users should state what they want, and DNSControl should do the rest
@ -93,7 +93,7 @@ Some examples:
# Opinion #6 If it is ambiguous in DNS, it is forbidden in DNSControl # Opinion #6 If it is ambiguous in DNS, it is forbidden in DNSControl
When there is ambiguity an expert knows what the system will do. When there is ambiguity an expert knows what the system will do.
Your coworkers should not be expected to be experts. (See [Opinion #2](#opinion-2--non-experts-should-be-able-to-safely-make-dns-changes)). Your coworkers should not be expected to be experts. (See [Opinion #2](#opinion-2-non-experts-should-be-able-to-safely-make-dns-changes)).
We would rather DNSControl error out than require users to be DNS experts. We would rather DNSControl error out than require users to be DNS experts.

6
documentation/writing-providers.md
View file

@ -281,9 +281,9 @@ dependencies.
Here are some last-minute things to check before you submit your PR. Here are some last-minute things to check before you submit your PR.
1. Run `go generate` to make sure all generated files are fresh. 1. Run `go generate` to make sure all generated files are fresh.
2. Make sure all appropriate documentation is current. (See [Step 8](#step-8--manual-tests)) 2. Make sure all appropriate documentation is current. (See [Step 8](#step-8-manual-tests))
3. Check that dependencies are current (See [Step 13](#step-13--dependencies)) 3. Check that dependencies are current (See [Step 13](#step-13-dependencies))
4. Re-run the integration test one last time (See [Step 7](#step-7--integration-test)) 4. Re-run the integration test one last time (See [Step 7](#step-7-integration-test))
## Step 15: After the PR is merged ## Step 15: After the PR is merged