-
Notifications
You must be signed in to change notification settings - Fork 41
Fix link bugs in readme.(#1025) #1025
New issue
Have a question 8000 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
Conversation
Thanks for the quick fix @ChengYueJia. The links you fixed were indeed broken when you navigate through github project. And your fixes fix them for that view, but it breaks on the website (when I tried manually). I think your PR/suggestions need to be addressed but let me try a couple of options and we can merge this by editing a little bit. |
@betarelease I'll waiting for the good news~~ |
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.
Thanks for the contribution @ChengYueJia but I don't think these changes affect/change the present readme file! So we might have to close the PR
@betarelease This PR doesn't introduce any significant changes, closing the PR! |
I will keep this open for a little. Basically we need to take in the changes that @ChengYueJia is suggesting. Just that they work on github and dont work that well on the website or vice versa. I need to test this on website and then confirm that we can take this in. |
@ChengYueJia I have not had a chance to test this yet. But will get to it today. (I need to run jekyll and then import a branch of pyrsia so needs a little setup to test). In the meanwhile, please join our slack channel and meet the team. Since you are interested in Rust we have a number of areas you can start contributing to. |
@betarelease Thanks for invitation. I'm glad to join in :). |
Hi @ChengYueJia I tested this with the generation of webpages from our docusaurus website. Basically I had to test it in two ways as follows:
I left comments inline to each of your changes and I think we can take 3 of the 4 changes as you made them. Can you please update the PR and I can approve it for merge. Thanks for your patience. It was a little tricky to test this out since we have not written down the steps, but I will write them down now. |
@betarelease Thanks for your patience and guide. |
Description
Ref #1018
Screenshots (optional)
PR Checklist
Code Contributions
cargo build --all-targets
successfully.cargo test --workspace
and everything passes.rustup update
.