-
Notifications
You must be signed in to change notification settings - Fork 547
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
doc: fixed broken links #4958
base: devel
Are you sure you want to change the base?
doc: fixed broken links #4958
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
Thanks for the PR.
there was doc folder restructure PR #4907, @yati1998 can you please check for any other broken links that might need updating beyond those listed here? |
Requested by iPraveenParihar in ceph#4958 Signed-off-by: 尤理衡 (Li-Heng Yu) <[email protected]>
Pull request has been modified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@seadog007 Can you please squash your commits into one? |
The deploy link in the README is broken. Fixed more broken links requested by iPraveenParihar in ceph#4958 Signed-off-by: 尤理衡 (Li-Heng Yu) <[email protected]>
The deploy link in the README is broken. Fixed more broken links requested by iPraveenParihar in ceph#4958 Signed-off-by: 尤理衡 (Li-Heng Yu) <[email protected]>
Pull request has been modified.
The deploy link in the README is broken. Fixed more broken links requested by iPraveenParihar in ceph#4958 Signed-off-by: 尤理衡 (Li-Heng Yu) <[email protected]>
Describe what this PR does
Fixed broken links for documents in 4 files.
Is there anything that requires special attention
Do you have any questions?
No
Is the change backward compatible?
No
Are there concerns around backward compatibility?
No
Provide any external context for the change, if any.
N/A
Related issues
Broken when #4907 merged
See also a6f1af4
Future concerns
N/A
Checklist:
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)