| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Partially addresses #16261.
|
| | |
|
| |
|
|
| |
Add instructions to developer documentation about initializing git submodules
before local build.
|
| | |
|
| |
|
|
|
| |
See https://github.blog/2021-09-01-improving-git-protocol-security-github/
Tell users to use https://
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upload docs to main branch of neps/devdocs
* Update `master` to `main` to be consistent with current state of renaming
* Remove badges from README
* Replace remaining instances of `master` with `main`
* Add back logo
* Fix CircleCI branch checks
* Fix GA branch name
* master->main in issue templates.
* master->main for 2 links to numpy archive.
* Change master to main in NEP 23
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: Simplify and update git setup page
Changed title from "Getting started with Git development"
to more specific "Setting up git for NumPy development"
Updated the outdated GitHub screenshot for forking button, added
more screenshots.
Simplified the narrative.
Fixed bad github links (always pointed to NumPy's github).
Clarified SSH setup, role, and effect on git remote -v.
Clarified meaning of "upstream" and "origin".
Replaced read of .git/config (platform-specific) with call to git config.
* DOC: Add links, remove section from PR #16671
Per suggestion, removed outdated advice on getting pull branches.
Added back rST anchors, should have left them in.
* DOC: Add page anchor for PR #16671
Add '.. _development-setup:' page anchor.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: Fixes for 18 broken links
This, with PR #16465, should fix nearly all the remaining broken links
on the site. 4 or 5 others should be easy to fix and just
need attention from someone more knowledgeable -- will
open an issue. For release notes with dead links,
I could usually find links on archive.org for roughly contemporary
versions.
* DOC: Update to "Fixes for 18 broken links #16472"
* Obsolete links, previously commented out, now deleted:
https://github.com/numpy/numpy/pull/16472#discussion_r433928958
* Semantic markup for reference to Python class:
https://github.com/numpy/numpy/pull/16472#discussion_r433553928
* Missing :ref: in internal link:
https://github.com/numpy/numpy/pull/16472#discussion_r433554484
Not included: Resolution on using external/internal doc link in .py:
https://github.com/numpy/numpy/pull/16472#discussion_r433554824
* DOC: Add internal link for 'Fixes for 18 broken links' PR #16472
Making reference [1] an internal link in function_base.py => numpy.vectorize.html
* DOC: Redirect 2 link fixes in PR #16472
* governance.rst link reverted
* ununcs.rst `overridden` link goes where it was meant to
per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed links for branch delete and graph visualizer.
Updated instructions for branch delete (git since 1.7.0 (Sept 2010)
has allowed --delete sted ':').
'Learn git' link pointed to Bitbucket instructions; replaced with GitHub
instructions.
Minor rewording in 'Pushing changes to the main repo'.
This is NOT a review of the page, only some fixes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
User- and non-user-facing typos.
Some source typos fixes as well.
Found via `codespell`.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The remote upstream fetch git-config command was missing two asterisks,
most likely lost in a markdown accident.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This is easier to get going, and is the recommended access method
by GitHub itself:
https://help.github.com/articles/which-remote-url-should-i-use/
Also add instructions for pulling from upstream including PRs
by default.
|
| |
|
|
|
|
|
|
|
| |
Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.
Release notes were left unchanged.
see issue #7986
|
| |
|
|
|
|
| |
Use the simpler `git fetch; ... upstream/master` approach instead of
updating the local master branch. Keeping the local master branch
in sync with upstream is usually not necessary.
|
| |
|
|
|
| |
The reason is that git log indents parts of the message and longer
lines will wrap. Linus has a post on this somewhere.
|
| |
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "Basic Workflow" section of the Development Workflow page was reorganized
to make it clearer to new users and remove/update old material.
Major changes:
- Moved the core developer notes. Core dev notes are confusing in basic usage
information. Updated a couple of the commands
- Added more commands and reorgaized the "New Feature Branch" section. Took
some text from "Rebasing" and moved it here, because it was redundant.
- Made many changes to the "Editing Workflow" to clarify commands. Moved some
git push stuff into this section as well.
- Moved pull request section to just after editing workflow. Removed outdated
images and simplified the text. Make code review requirements explicit.
- Moved rebasing and troubleshooting sections to the end. Could add more here
later.
- Links renamed and broken link removed.
|
| | |
|
| |
|
|
| |
Now is as good a time as any with open PR's at a low.
|
| | |
|
| |
|
|
| |
This commit address comments from Charles on PR #455.
|
| |
|
|
|
| |
Recommend to update master before creating your feature branch.
Thanks to Nicky van Foreest for feedback on the dev-guide.
|
| |
|
|
|
| |
This section is outdated, and following it pretty much ensures that your
patches will languish in Trac.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
