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

docs: fix broken links #3989

Closed
wants to merge 1 commit into from
Closed

docs: fix broken links #3989

wants to merge 1 commit into from

Conversation

blkperl
Copy link
Contributor

@blkperl blkperl commented Dec 6, 2024

fixes #3983

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

I fixed most of the warnings shown when running

make serve-docs

fixes argoproj#3983

Signed-off-by: william.vanhevelingen <[email protected]>
Copy link

sonarqubecloud bot commented Dec 6, 2024

@blkperl
Copy link
Contributor Author

blkperl commented Dec 6, 2024

@zachaller do you know where the link is set for these generated docs?

WARNING -  Doc file 'generated/notification-services/teams.md' contains a link '../templates.md', but the target
           'generated/templates.md' is not found among documentation files.

@zachaller zachaller self-requested a review December 6, 2024 15:49
zachaller
zachaller previously approved these changes Dec 6, 2024
@zachaller zachaller self-requested a review December 6, 2024 16:05
@zachaller
Copy link
Collaborator

zachaller commented Dec 6, 2024

I think think these links are actually broken on the hosted site: https://argo-rollouts.readthedocs.io/en/latest/FAQ/

I only checked the best practices link

Copy link
Contributor

github-actions bot commented Dec 6, 2024

Published E2E Test Results

  4 files    4 suites   3h 13m 54s ⏱️
113 tests 104 ✅  7 💤 2 ❌
456 runs  424 ✅ 28 💤 4 ❌

For more details on these failures, see this check.

Results for commit f9233a3.

Copy link
Contributor

github-actions bot commented Dec 6, 2024

Published Unit Test Results

2 293 tests   2 293 ✅  2m 59s ⏱️
  128 suites      0 💤
    1 files        0 ❌

Results for commit f9233a3.

@blkperl
Copy link
Contributor Author

blkperl commented Dec 6, 2024

I think think these links are actually broken on the hosted site: https://argo-rollouts.readthedocs.io/en/latest/FAQ/

I only checked the best practices link

What do you mean they are broken on the hosted site?

@zachaller
Copy link
Collaborator

You edited the FAQ's best practices link but you will notice it's not broken here https://argo-rollouts.readthedocs.io/en/latest/FAQ/

@zachaller zachaller dismissed their stale review December 6, 2024 18:03

links are not broken on readthe docs

@blkperl
Copy link
Contributor Author

blkperl commented Dec 6, 2024

You edited the FAQ's best practices link but you will notice it's not broken here https://argo-rollouts.readthedocs.io/en/latest/FAQ/

Oh interesting, I guess make serve-docs throws a warning and Goland shows an error but then when they are served it becomes a 404.

@blkperl
Copy link
Contributor Author

blkperl commented Dec 6, 2024

Well this needs more work, so i will close it for now.

@blkperl blkperl closed this Dec 6, 2024
@blkperl blkperl deleted the fix_3983 branch December 6, 2024 18:28
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.

broken link in https://argoproj.github.io/argo-rollouts/features/canary/ ( Anti Affinity document )
2 participants