Skip to content
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

Add hyperlinks and paths validation. #148

Closed
wants to merge 49 commits into from
Closed

Add hyperlinks and paths validation. #148

wants to merge 49 commits into from

Conversation

ZePan110
Copy link
Collaborator

No description provided.

@ZePan110
Copy link
Collaborator Author

@ctao456 Can you help check

[ctao456](https://github.com/ctao456), [alexsin368](https://github.com/alexsin368), [YuningQiu](https://github.com/YuningQiu), [louie-tsai](https://github.com/louie-tsai)
The tool reports an error when checking, I can't find where this link points to.
image

@ctao456
Copy link
Contributor

ctao456 commented Sep 19, 2024

Hi @ZePan110 I submitted a pull request to fix this invalid link.
#149

.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Show resolved Hide resolved
@ZePan110
Copy link
Collaborator Author

ZePan110 commented Sep 19, 2024

@ctao456

Hi @ZePan110 I submitted a pull request to fix this invalid link. #149
Still not accessible. BTW, Should we put such private links?
image
image

@mkbhanda
Copy link
Collaborator

mkbhanda commented Sep 19, 2024

Private links --- given this is for documentation .. am guessing there should be no private links! Would not help user. The error code should be adequate to prompt them how to fix. Or add a sentence .. perhaps you incorrectly provided a restricted link or something. I am ambivalent about emails .. what if it is a vulnerability reporting link and it bounces. Put that as issue and lets deal with it in the future. Thank you for this link correctness checker script.

@ctao456
Copy link
Contributor

ctao456 commented Sep 19, 2024

@ctao456

Hi @ZePan110 I submitted a pull request to fix this invalid link. #149
Still not accessible. BTW, Should we put such private links?
image
image

In order for the pr to take effect, I need 2 approvals first.

Copy link
Collaborator

@mkbhanda mkbhanda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please address earlier comment about not retrying for certain error codes like 400 range.

.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
@ZePan110
Copy link
Collaborator Author

@ctao456

Hi @ZePan110 I submitted a pull request to fix this invalid link. #149
Still not accessible. BTW, Should we put such private links?
image
image

In order for the pr to take effect, I need 2 approvals first.
The link doesn't seem to exist
image

Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
@dbkinder
Copy link
Contributor

Hi @ZePan110 I submitted a pull request to fix this invalid link. #149

PR approved and merged, thanks.

Copy link
Contributor

@dbkinder dbkinder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments

.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
.github/workflows/pr-path-detection.yml Outdated Show resolved Hide resolved
@ZePan110
Copy link
Collaborator Author

I've deleted that test folder. But we should have a way to exclude test issues from your CI checking.

The tool's is to expose invalid links during integration, I don't quite understand what you mean by exclusion.

This directory held tests for scripts that do manipulation of markdown
files to prepare for doc publishing.  They were causing problems for the
CI testing looking for broken links, so remove the test folder.

Signed-off-by: David B. Kinder <[email protected]>
@ZePan110
Copy link
Collaborator Author

Due to the excessive discussion, in order to facilitate review, we will recreate the #177
and continue working on this.

@ZePan110 ZePan110 closed this Sep 25, 2024
ZePan110 and others added 23 commits September 25, 2024 18:21
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
Signed-off-by: ZePan110 <[email protected]>
@ZePan110 ZePan110 deleted the zepan/dev branch November 4, 2024 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants