TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions

Fix "GitHub" capitalization (#6806)

Browse source 
Signed-off-by: TAKAHASHI Shuuji <shuuji3@gmail.com>
This commit is contained in:
TAKAHASHI Shuuji 2024-10-02 01:15:42 +09:00 • committed by GitHub
parent 022fbd8735
commit 5100feebd3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.github/SECURITY.md vendored
View file

@ -24,7 +24,7 @@ The initial Product Security Team will consist of the set of maintainers that vo
### Private Disclosure Processes ### Private Disclosure Processes
If you find a security vulnerability or any security related issues, If you find a security vulnerability or any security related issues,
please DO NOT file a public issue. Do not create a Github issue. please DO NOT file a public issue. Do not create a GitHub issue.
Instead, send your report privately to security@coredns.io. Instead, send your report privately to security@coredns.io.
Security reports are greatly appreciated and we will publicly thank you for it. Security reports are greatly appreciated and we will publicly thank you for it.
@ -94,7 +94,7 @@ so that a realistic timeline can be communicated to users.
**Disclosure of Forthcoming Fix to Users** (Completed within 1-7 days of Disclosure) **Disclosure of Forthcoming Fix to Users** (Completed within 1-7 days of Disclosure)
- The Fix Lead will create a github issue in CoreDNS project to inform users that a security vulnerability - The Fix Lead will create a GitHub issue in CoreDNS project to inform users that a security vulnerability
has been disclosed and that a fix will be made available, with an estimation of the Release Date. has been disclosed and that a fix will be made available, with an estimation of the Release Date.
It will include any mitigating steps users can take until a fix is available. It will include any mitigating steps users can take until a fix is available.

4
GOVERNANCE.md
View file

@ -36,7 +36,7 @@ maintainers.
Every Maintainer is listed in the Every Maintainer is listed in the
[CODEOWNERS](https://github.com/coredns/coredns/blob/master/CODEOWNERS) [CODEOWNERS](https://github.com/coredns/coredns/blob/master/CODEOWNERS)
file, with their Github handle. file, with their GitHub handle.
A Maintainer should be a member of `maintainers@coredns.io`, although this is not a hard requirement. A Maintainer should be a member of `maintainers@coredns.io`, although this is not a hard requirement.
@ -107,7 +107,7 @@ The decision-making process should be transparent to adhere to the CoreDNS Code
All proposals, ideas, and decisions by maintainers or the steering committee All proposals, ideas, and decisions by maintainers or the steering committee
should either be part of a GitHub issue or PR, or be sent to `maintainers@coredns.io`. should either be part of a GitHub issue or PR, or be sent to `maintainers@coredns.io`.
## Github Project Administration ## GitHub Project Administration
The __coredns__ GitHub project maintainers team reflects the list of Maintainers. The __coredns__ GitHub project maintainers team reflects the list of Maintainers.

2
Makefile.docker
View file

@ -68,7 +68,7 @@ endif
@mkdir -p build/docker @mkdir -p build/docker
@# 1. Copy appropriate coredns binary to build/docker/<arch> @# 1. Copy appropriate coredns binary to build/docker/<arch>
@# 2. Copy Dockerfile into the correct dir as well. @# 2. Copy Dockerfile into the correct dir as well.
@# 3. Unpack the tgz from github into 'coredns' binary. @# 3. Unpack the tgz from GitHub into 'coredns' binary.
for arch in $(LINUX_ARCH); do \ for arch in $(LINUX_ARCH); do \
mkdir build/docker/$${arch}; \ mkdir build/docker/$${arch}; \
curl -L $(GITHUB)/v$(VERSION)/coredns_$(VERSION)_linux_$${arch}.tgz > build/docker/$${arch}/coredns.tgz && \ curl -L $(GITHUB)/v$(VERSION)/coredns_$(VERSION)_linux_$${arch}.tgz > build/docker/$${arch}/coredns.tgz && \

4
README.md
View file

@ -256,9 +256,9 @@ When no transport protocol is specified the default `dns://` is assumed.
## Community ## Community
We're most active on Github (and Slack): We're most active on GitHub (and Slack):
- Github: <https://github.com/coredns/coredns> - GitHub: <https://github.com/coredns/coredns>
- Slack: #coredns on <https://slack.cncf.io> - Slack: #coredns on <https://slack.cncf.io>
More resources can be found: More resources can be found:

2
man/coredns-dnstap.7
View file

@ -71,7 +71,7 @@ dnstap tcp://127.0.0.1:6000 full
.SH "COMMAND LINE TOOL" .SH "COMMAND LINE TOOL"
.PP .PP
Dnstap has a command line tool that can be used to inspect the logging. The tool can be found Dnstap has a command line tool that can be used to inspect the logging. The tool can be found
at Github: https://github.com/dnstap/golang-dnstap at GitHub: https://github.com/dnstap/golang-dnstap
\[la]https://github.com/dnstap/golang-dnstap\[ra]. It's written in Go. \[la]https://github.com/dnstap/golang-dnstap\[ra]. It's written in Go.
.PP .PP

2
plugin/dnstap/README.md
View file

@ -101,7 +101,7 @@ dnstap tcp://example.com:6000
## Command Line Tool ## Command Line Tool
Dnstap has a command line tool that can be used to inspect the logging. The tool can be found Dnstap has a command line tool that can be used to inspect the logging. The tool can be found
at Github: <https://github.com/dnstap/golang-dnstap>. It's written in Go. at GitHub: <https://github.com/dnstap/golang-dnstap>. It's written in Go.
The following command listens on the given socket and decodes messages to stdout. The following command listens on the given socket and decodes messages to stdout.