Skip to content

Commit 02a9fb9

Browse files
authored
Merge pull request #1225 from consideRatio/readme-pr
FIXES #1224 - Added contribution section to README.md
2 parents 642bc29 + 35d3927 commit 02a9fb9

File tree

4 files changed

+62
-4
lines changed

4 files changed

+62
-4
lines changed

CHANGELOG.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,16 @@ Unreleased (aka. GitHub master)
2121
This is where each new PR to the project should add a summary of its changes,
2222
which makes it much easier to fill in each release's changelog :)
2323

24+
Repo-level stuff:
25+
26+
- Added CONTRIBUTING.md
27+
[#1224](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/pull/1224)
28+
[@consideratio](https://github.com/consideratio)
29+
30+
New features and bugfixes:
31+
32+
- `init_cell`
33+
* Warning dialog now always relevant, fixes [#1223](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/issues/1223). [#1226](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/pull/1226) [@consideratio](https://github.com/consideratio)
2434

2535
0.4.0
2636
-----
@@ -118,10 +128,6 @@ New features and bugfixes:
118128
- `code_prettify` Update `code_prettify.yaml`
119129
[#1162](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/pull/1162)
120130
[@fehiepsi](https://github.com/fehiepsi)
121-
- `init_cell`
122-
* Warning dialog now always relevant, fixes [#1223].(https://github.com/ipython-contrib/jupyter_contrib_nbextensions/issues/1223)
123-
[#1226](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/pull/1226)
124-
[@consideratio](https://github.com/consideratio)
125131

126132

127133
0.3.3

CONTRIBUTING.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributing to jupyter notebook nbextensions
2+
3+
We are super happy that you intend to contribute to the nbextensions! You can discuss improvements in issues and implement them in pull requests.
4+
5+
## Create an issue
6+
7+
Do not hesitate to open up an issue, you can discuss bugs, improvements or new extensions in them. Creating an issue is a good starting point for code contributions. The community can support you with experience of similar extensions, pros and cons, what to look for etc.
8+
9+
Here is an example issue of how @benelot did it that worked pretty smoothly: [#1193](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/issues/1193)
10+
11+
## Setup development
12+
13+
For small things like fixing typos in documentation, you can [make edits through GitHub](https://help.github.com/articles/editing-files-in-another-user-s-repository/), which will handle forking and making a pull request (PR) for you. For anything bigger or more complex, you'll probably want to set up a development environment, a quick procedure for which is as folows:
14+
15+
1. __Fork and clone__
16+
First fork this repo, then clone your fork. In this way you become prepared to make a pull request.
17+
18+
```shell
19+
# clone your fork
20+
git clone https://github.com/<your-github-username>/jupyter_contrib_nbextensions.git
21+
cd jupyter_contrib_nbextensions
22+
```
23+
24+
2. __Setup__
25+
26+
If you're using python in combination with some form of virtual environment (e.g. conda, virtualenv), make sure you have the correct environment (the one from which you run `jupyter notebook`) active before running these commands!
27+
28+
```shell
29+
# run from the main directory, where setup.py is
30+
pip install --editable .
31+
32+
# on windows, remove the --symlink flag and re-run the command each time you make changes
33+
jupyter-contrib-nbextension install --sys-prefix --symlink
34+
```
35+
36+
## Create an extension
37+
38+
Add a folder with the name of your new extension to [jupyter_contrib_nbextensions/nbextensions](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/tree/master/src/jupyter_contrib_nbextensions/nbextensions). Check out the [Jupyter Notebook extension structure link](http://jupyter-contrib-nbextensions.readthedocs.io/en/latest/internals.html) to know what has to be in that folder and what the general conventions are.
39+
40+
## Create a pull request
41+
42+
As you are ready with your code contribution, make a pull-request to the main repo and briefly explain what you have done.
43+
44+
Here is an example pull request of how @benelot did it that worked super well: [#1213](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/pull/1213)
45+
46+
Please also update the [unreleased section](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/blob/master/CHANGELOG.md#unreleased-aka-github-master) of the [CHANGELOG.md](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/blob/master/CHANGELOG.md) to note what you've added or fixed.

MANIFEST.in

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
# explicit includes
22
include COPYING.rst
33
include README.md
4+
include CONTRIBUTING.md
45
include CHANGELOG.md
56
include tox.ini
67
include .bumpversion.cfg

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -243,6 +243,11 @@ Each notebook extension typically has its own directory named after the extensio
243243

244244
For further details, see [the documentation at jupyter-contrib-nbextensions.readthedocs.io](http://jupyter-contrib-nbextensions.readthedocs.io/en/latest/internals.html).
245245

246+
Contributing
247+
============
248+
249+
To learn how to setup a development enivornment and contribution guidelines, see [CONTRIBUTING.md](./CONTRIBUTING.md).
250+
246251
Changes
247252
=======
248253

0 commit comments

Comments
 (0)