-
Notifications
You must be signed in to change notification settings - Fork 69
Fix link to contribution docs #440
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| Please check out [our documentation's contributing guide](https://jupytergis.readthedocs.io/en/latest/contributing.html). | ||
| Please check out [our documentation's contributing guide](https://jupytergis.readthedocs.io/en/latest/contributor_guide/index.html). |
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -15,7 +15,7 @@ By the end of this tutorial, you will: | |||||
|
|
||||||
| :::{admonition} Prerequisites | ||||||
| :class: warning | ||||||
| Before beginning this tutorial, JupyterGIS must be installed on your computer (see [Installation instructions](https://geojupyter.github.io/jupytergis/install.html)) or you can use an online version of JupyterGIS (such as [](https://geojupyter.github.io/jupytergis/lite/lab/index.html?path=france_hiking.jGIS/)). | ||||||
| Before beginning this tutorial, JupyterGIS must be installed on your computer (see [Installation instructions](https://jupytergis.readthedocs.io/en/latest/user_guide/install.html)) or you can use an online version of JupyterGIS (such as [](https://geojupyter.github.io/jupytergis/lite/lab/index.html?path=france_hiking.jGIS/)). | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Woopsie! Should this be an internal link instead of a full HTTP URL so that the check links job can catch this type of mistake?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure actually, I don't have a strong opinion on it. Thankfully check-links allows us to catch this issue early anyway. And those links are not likely to change every month. So I guess it's not a big deal?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure I understand! Just to be really clear, I'm suggesting:
Suggested change
Then if we move documents around in a PR (like #411), the check-links check for that PR would fail.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, got it 👍🏽 But the nice thing about keeping URLs to the docs is that when you click on it from the repo you get directed to the docs deployment.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are there other links in the docs that are full HTTPs urls? As far as I could tell, we're using relative links everywhere else. The thing I'm confused about most right now is why this one is different. Since we have so much syntax in the docs that GitHub can't understand, I assumed it was a non-goal to serve folks who are viewing the docs in GitHub! |
||||||
| ::: | ||||||
|
|
||||||
| ## Introduction to JupyterGIS | ||||||
|
|
||||||
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.
D'oh! Of course. Thanks :)