summaryrefslogtreecommitdiff
path: root/doc/source/dev/gitwash
Commit message (Collapse)AuthorAgeFilesLines
* DOC: changes from reviewmattip2019-04-232-11/+3
|
* DOC: reorganize developer docs, use scikit-image as a base for changemattip2019-04-217-565/+28
|
* HTTP -> HTTPS, and other linkrot fixesMike Toews2018-06-162-35/+35
|
* MAINT: Misc. typos (#11005)luzpaz2018-04-301-1/+1
| | | | | | | | | User- and non-user-facing typos. Some source typos fixes as well. Found via `codespell`.
* add missing glossary entries and link in missing documentmattip2018-04-111-0/+1
|
* DOC: cosmetic changes, document need for python3.6 to build docsmattip2018-04-101-3/+3
|
* DOC: promote development_workflow, make howtos visiblemattip2018-04-102-1/+1
|
* DOC: Fix missing asterisks in git development_setup doc pageAndras Deak2017-06-271-1/+1
| | | | | The remote upstream fetch git-config command was missing two asterisks, most likely lost in a markdown accident.
* git:// to https://Shitian Ni2017-05-252-16/+5
|
* updated development git document on protocolsShitian Ni2017-05-252-0/+6
|
* DOC: update docs and comments for move of mailing list to python.orgRalf Gommers2017-03-261-31/+1
|
* DOC: add BENCH prefix to documented commit prefixesJulian Taylor2017-03-251-0/+1
|
* DOC: Fix typosJakub Wilk2017-03-171-1/+1
|
* DOC: change development instructions from SSH to HTTPS access.Ralf Gommers2016-10-241-5/+37
| | | | | | | | | 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.
* change all non-code instances of Numpy to NumPyPierre de Buyl2016-09-061-2/+2
| | | | | | | | | Instances remain for NumpyVersion and Numpy.rec.fromarrays that are references to code. Release notes were left unchanged. see issue #7986
* DOC: dev: stop recommending keeping local master updated with upstream/masterPauli Virtanen2016-02-211-94/+69
| | | | | | 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.
* DOC: Commit message lines should not excede 72 characters.Charles Harris2015-05-251-1/+1
| | | | | The reason is that git log indents parts of the message and longer lines will wrap. Linus has a post on this somewhere.
* DOC: add "build and test" section to developer guide. Closes gh-5465.Ralf Gommers2015-01-201-1/+1
| | | | [ci skip]
* DOC: Update Development Workflow PageRyan Nelson2015-01-104-193/+166
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* DOC: Notes on backporting.Blake Griffith2013-10-102-1/+62
|
* STY: Giant whitespace cleanup.Charles Harris2013-08-185-12/+9
| | | | Now is as good a time as any with open PR's at a low.
* move to www.numpy.orgSandro Tosi2012-12-301-1/+1
|
* DOC: expand sections on commit messages and merging/rebasing in the devguide.Ralf Gommers2012-09-231-2/+16
| | | | This commit address comments from Charles on PR #455.
* DOC: one more edit to the dev-guide.Ralf Gommers2012-09-221-1/+7
| | | | | Recommend to update master before creating your feature branch. Thanks to Nicky van Foreest for feedback on the dev-guide.
* DOC: remove section "Patching" from dev-guide.Ralf Gommers2012-09-224-133/+6
| | | | | This section is outdated, and following it pretty much ensures that your patches will languish in Trac.
* DOC: a few edits to make "Development Workflow" in the dev guide clearer.Ralf Gommers2012-09-221-12/+13
|
* DOC: document in dev-guide how to write a good commit message.Ralf Gommers2012-09-221-0/+28
|
* DOC: merge wiki docs - edits under doc/.Ralf Gommers2012-07-071-4/+3
|
* DOC: merge wiki doc edits.Ralf Gommers2012-03-031-2/+5
|
* DOC: dev: update also the overviewPauli Virtanen2010-10-291-2/+3
|
* DOC: dev: update instructions on sending patchesPauli Virtanen2010-10-291-1/+6
|
* DOC: dev: try to improve Git workflow docsPauli Virtanen2010-10-1910-121/+355
|
* DOC: regenerate gitwash docsPauli Virtanen2010-10-0417-0/+871