-
Notifications
You must be signed in to change notification settings - Fork 45
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
Images not showing up correctly on Github #13
Comments
I'm having the same problem! |
In order to troubleshoot, you need to either push your commit to your |
@Bobicheng-Zhang @avajurden Most likely it is because of the image URL. If the image exists in your laptop and not in Github then you need to push the image to GitHub. Also, reply with the markdown which you have written in Readme file. |
I have pushed the commit to branch homework1 in my hw01 fork.
This is what I used. Since I pushed the image to Github, I also tried using the file path on Github, but that didn't work either. |
@Bobicheng-Zhang Your image url is |
Instead stage and commit the image inside of your |
@mayank-kgp I also copied the file path Github gave me but it didn't work either. |
@Bobicheng-Zhang Make the url - IMG_0929.jpg or /IMG_0929.jpg. |
It worked! Thank you! @bensoltoff @mayank-kgp |
@Bobicheng-Zhang You don't need to do branching as there are separate repositories for each homework which you need to fork every week. However, it doesn't matter. |
Any idea why my image would show up in my own git (https://github.com/abbygirlrose/hw01) but not inside the pull request (cfss-fa20/hw01@aff1b98?short_path=04c6e90#diff-04c6e90faac2675aa89e2176d2eec7d8)? |
@abbygirlrose Because the image file exist on your own git. But it is not on the uc-cfss Github repo yet. You have sent the image as a part of the pull request. So once your pull request is merged then it will be shown. |
hm thanks! |
I am having trouble displaying an image on Github even though it shows up on RStudio preview perfectly. The error message I received after clicking on the picture is 404. Is anyone else having this problem?
The text was updated successfully, but these errors were encountered: