Skip to content

[clang-tidy][NFC] Fix broken link in documentation of cert-env33-c #90216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 26, 2024

Conversation

NagyDonat
Copy link
Contributor

It seems that the description of the SEI CERT rules was moved from www.securecoding.cert.org to wiki.sei.cmu.edu and the page IDs were not preserved during the transition.

However, the old domain name redirects to the new one and permalinks derived from the name of the rule still work, so I kept using the old domain name to be consistent with other documentation files using it.

It seems that the description of the SEI CERT rules was moved from
`www.securecoding.cert.org` to `wiki.sei.cmu.edu` and the page IDs were
not preserved during the transition.

However, the old domain name redirects to the new one and permalinks
derived from the name of the rule still work, so I kept using the old
domain name to be consistent with other documentation files using it.
@llvmbot
Copy link
Member

llvmbot commented Apr 26, 2024

@llvm/pr-subscribers-clang-tools-extra

Author: None (NagyDonat)

Changes

It seems that the description of the SEI CERT rules was moved from www.securecoding.cert.org to wiki.sei.cmu.edu and the page IDs were not preserved during the transition.

However, the old domain name redirects to the new one and permalinks derived from the name of the rule still work, so I kept using the old domain name to be consistent with other documentation files using it.


Full diff: https://github.com/llvm/llvm-project/pull/90216.diff

1 Files Affected:

  • (modified) clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst (+1-1)
diff --git a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
index c5321b07f7f84d..9271c9ecccc00c 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
@@ -10,4 +10,4 @@ but does not actually attempt to execute a command.
 
 This check corresponds to the CERT C Coding Standard rule
 `ENV33-C. Do not call system()
-<https://www.securecoding.cert.org/confluence/pages/viewpage.action?pageId=2130132>`_.
+<https://www.securecoding.cert.org/confluence/display/c/ENV33-C.+Do+not+call+system()>`_.

@llvmbot
Copy link
Member

llvmbot commented Apr 26, 2024

@llvm/pr-subscribers-clang-tidy

Author: None (NagyDonat)

Changes

It seems that the description of the SEI CERT rules was moved from www.securecoding.cert.org to wiki.sei.cmu.edu and the page IDs were not preserved during the transition.

However, the old domain name redirects to the new one and permalinks derived from the name of the rule still work, so I kept using the old domain name to be consistent with other documentation files using it.


Full diff: https://github.com/llvm/llvm-project/pull/90216.diff

1 Files Affected:

  • (modified) clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst (+1-1)
diff --git a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
index c5321b07f7f84d..9271c9ecccc00c 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
@@ -10,4 +10,4 @@ but does not actually attempt to execute a command.
 
 This check corresponds to the CERT C Coding Standard rule
 `ENV33-C. Do not call system()
-<https://www.securecoding.cert.org/confluence/pages/viewpage.action?pageId=2130132>`_.
+<https://www.securecoding.cert.org/confluence/display/c/ENV33-C.+Do+not+call+system()>`_.

@PiotrZSL
Copy link
Member

If there is redirection, then we could switch all links to new domain.

@NagyDonat
Copy link
Contributor Author

I'm merging this now, because switching all links to the new domain name has no immediate advantages (as long as the current one works) and would touch a dozen additional files. (By the way, the currently used domain name is also referenced in a LICENSE.TXT file and I didn't want to touch that.)

@NagyDonat NagyDonat merged commit 2d09ac4 into llvm:main Apr 26, 2024
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants