reference images #1 #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
another way to reference images
|
Once you created and pushed the gh-pages branch you can examine the result at https://neon22.github.io/micropython-examine-mem-maps/D3-memmaps-v1.html Link to these pages from your readme and you are done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Within the proposed image reference you'll see
/master/, this part should be a branch name or the SHA of a commit. SHA's won't cause broken links when you (re)move an image you forgot you linked somewhere, a branch name doesn't require to change the reference when you change the image.Using github pages requires only to rename your master branch into gh-pages and make it the default branch on the settings page of your project.