Skip to content

fix: bad links #487

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
May 12, 2025
Merged

fix: bad links #487

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dd8814d
fix: bad links
lwasser May 12, 2025
b057997
Apply suggestions from code review
lwasser May 12, 2025
f347420
more broken things
lwasser May 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion TRANSLATING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ If a language is ready to go live, the maintainers will add the language code to

When the guide is built for release in CI, Sphinx will also generate the translated versions of the guide for the languages in the `RELEASE_LANGUAGES` list.

Translations are released in the same way as the English version of the guide, and the translated versions will be available in folders named after the language code. For example, the Spanish translation will be available in [https://www.pyopensci.org/python-package-guide/es/](https://www.pyopensci.org/python-package-guide/es/).
Translations are released in the same way as the English version of the guide, and the translated versions will be available in folders named after the language code. For example, the Spanish translation will be available at: `https://www.pyopensci.org/python-package-guide/es/` when it is published online.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link is broken because spanish isn't published yet.


## Frequently Asked Questions (FAQ)

Expand Down
2 changes: 1 addition & 1 deletion bibliography.bib
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,6 @@ @misc{creativecommonsShareAlikeCompatibilityGPLv32015
year = {2015},
month = sep,
journal = {Creative Commons Wiki},
url = {https://wiki.creativecommons.org/wiki/ShareAlike\_compatibility:\_GPLv3},
url = {https://wiki.creativecommons.org/wiki/ShareAlike_compatibility:_GPLv3},
urldate = {2024-03-02}
}
2 changes: 1 addition & 1 deletion documentation/repository-files/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ name: moving-pandas-github-community
width: 80%
alt: Image showing that the MovingPandas GitHub repository community health page with green checks next to each file including a description, README, code of conduct, contributing, license and issue templates. Note that Security policy has a yellow circle next to it as that is missing from the repo.
---
GitHub community health looks for a readme file among other elements when it evaluates the community level health of your repository. This example is from the [MovingPandas GitHub repo](https://github.com/anitagraser/movingpandas/community) *(screen shot taken Nov 23 2022)*
GitHub community health looks for a readme file among other elements when it evaluates the community level health of your repository. This example is from the [MovingPandas GitHub repo](https://github.com/movingpandas/movingpandas/community) *(screen shot taken Nov 23 2022)*
```

[Snyk](https://snyk.io/advisor/python) is another well-known company that
Expand Down
4 changes: 2 additions & 2 deletions documentation/repository-files/license-files.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ bibliography:

(license-file)=

# License files for scientific Python open source software
# License files for Python open source software

:::{button-link} <https://www.pyopensci.org/about-peer-review/>
:color: primary
Expand Down Expand Up @@ -69,7 +69,7 @@ in some cases the license that you want is not available through that online
process.

:::{admonition} License recommendations from the SciPy package
[The SciPy documentation has an excellent overview of licenses.](https://docs.scipy.org/doc/scipy/dev/core-dev/index.html#licensing). One of the key elements
[The SciPy documentation has an excellent overview of licenses.](https://docs.scipy.org/doc/scipy/dev/core-dev/index.html#licensing) One of the key elements
that these docs recommend is ensuring that the license that you select is
compatible with licenses used in many parts of the scientific Python ecosystem.
Below is a highlight of this text which outlines license that are compatible
Expand Down
2 changes: 1 addition & 1 deletion package-structure-code/code-style-linting-format.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ You type and run:
The pre-commit workflow begins with you adding files that have changes to be
staged in git. Next, you'd run git commit. When you run git commit, the pre-commit
hooks will then run. In this example, Black, the code formatter and flake8, a linter both run. If all of the files pass Black and flake8 checks, then your commit will be recorded. If they don't, the commit is canceled. You will have to fix any flake8 issues,
and then re-add / stage the files to be committed. [_Image Source_](https://ljvmiranda921.github.io/notebook/2018/06/21/precommits-using-black-and-flake8/*)
and then re-add / stage the files to be committed. [_Image Source_](https://ljvmiranda921.github.io/notebook/2018/06/21/precommits-using-black-and-flake8/)
:::

<!-- For instance, if you setup the Black code formatter as a pre-commit hook,
Expand Down
Loading