DOC: Crosslinking to Gitpod guide #19185
Merged
Conversation
|
Looks like your editor is set up to wrap lines instead of breaking them. We try to keep line length < 80 characters with hard line breaks. |
|
@charris Thanks for the information! I'm using Gitpod, so I've added automatic word wrapping. I've fixed the tangled commits with Melissa's help and added the line breaks. |
charris
merged commit dae36b3
into
numpy:main
36 checks passed
36 checks passed
azure-pipeline numpy.numpy (ComprehensiveTests Linux_Python_38_32bit_full_with_asserts)
ComprehensiveTests Linux_Python_38_32bit_full_with_asserts succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Linux_gcc48)
ComprehensiveTests Linux_gcc48 succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Windows Python37-64bit-full)
ComprehensiveTests Windows Python37-64bit-full succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Windows Python38-32bit-fast)
ComprehensiveTests Windows Python38-32bit-fast succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Windows Python38-64bit-full)
ComprehensiveTests Windows Python38-64bit-full succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Windows Python39-32bit-fast)
ComprehensiveTests Windows Python39-32bit-fast succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests Windows Python39-64bit-full)
ComprehensiveTests Windows Python39-64bit-full succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests WindowsFast Python37-32bit-fast)
ComprehensiveTests WindowsFast Python37-32bit-fast succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests macOS Python37)
ComprehensiveTests macOS Python37 succeeded
Details
azure-pipeline numpy.numpy (ComprehensiveTests macOS Python37-ILP64)
ComprehensiveTests macOS Python37-ILP64 succeeded
Details
azure-pipeline numpy.numpy (InitialTests Linux_baseline_native)
InitialTests Linux_baseline_native succeeded
Details
|
Thanks @MarsBarLee . |
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.
A very helpful page, Using Gitpod for NumPy Development, was not crosslinked in two other pages about building NumPy. The two pages are 'Building from source' and 'Building the NumPy API and reference docs'.
Please let me know if the added wording about building the source is technically correct.
I also had a commit hiccup. I modified my commit messages after pushing (using rebase and --force-with-lease), and it looks like this also brought @Mukulikaa recent commits with this PR. It looks we pushed our commits around the same time but from our own forks and branches. We worked on different pages, her on 'absolute-beginners.html' and mine are 'howto_build_docs.rst' and 'building.rst'.
However, her most recent commit was also on building.rst, but those changes are not in this commit.
I'm not sure how to detangle that, so would appreciate any help. :)