Skip to content
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

Jump to bottom

DOC: Update documentation to reference SSH #26343

Closed
wants to merge 5 commits into from
Closed

DOC: Update documentation to reference SSH #26343

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5b91105
Update documentation to reference SSH
ogidig5 Apr 24, 2024
34ab2c7
Merge branch 'main' of https://github.com/numpy/numpy
ogidig5 May 3, 2024
1adf8d9
Removed all the typical GitHub interactions from the documentation [s…
ogidig5 May 3, 2024
3a8bad6
Merge branch 'main' of https://github.com/numpy/numpy
ogidig5 May 4, 2024
bf6fb99
DOC:The authentication instructions are incorrect and outdated. [skip…
ogidig5 May 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 3 additions & 6 deletions doc/source/dev/index.rst
View file
Open in desktop
Expand Up @@ -87,16 +87,13 @@ Here's the short summary, complete TOC links are below:
* Push your changes back to your fork on GitHub::

git push origin linspace-speedups

* Enter your GitHub username and password (repeat contributors or advanced
users can remove this step by connecting to GitHub with SSH).


* Go to GitHub. The new branch will show up with a green Pull Request
button. Make sure the title and message are clear, concise, and self-
explanatory. Then click the button to submit it.

* If your commit introduces a new feature or changes functionality, post on
the `mailing list`_ to explain your changes. For bug fixes, documentation
* If your commit introduces a new feature or changes functionality, post
on the `mailing list`_ to explain your changes. For bug fixes, documentation
updates, etc., this is generally not necessary, though if you do not get
any reaction, do feel free to ask for review.

Expand Down