FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks sion available from within JavaScript. 3. Commit and tag the release with the current version number: 67 Jupyter Notebook Documentation, Release 5.1.0 git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks sion available from within JavaScript. 3. Commit and tag the release with the current version number: 67 Jupyter Notebook Documentation, Release 5.0.0 git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks available from within JavaScript. 3. Commit and tag the release with the current version number: 67 Jupyter Notebook Documentation, Release 5.3.0.dev git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks makes the notebook version available from within JavaScript. 3. Commit and tag the release with the current version number: git commit -am "release $VERSION" git tag $VERSION 4. You are now ready to

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks makes the notebook version available from within JavaScript. 3. Commit and tag the release with the current version number: git commit -am "release $VERSION" git tag $VERSION 4. You are now ready to

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks makes the notebook version available from within JavaScript. 3. Commit and tag the release with the current version number: git commit -am "release $VERSION" git tag $VERSION 4. You are now ready to

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks sion available from within JavaScript. 3. Commit and tag the release with the current version number: 69 Jupyter Notebook Documentation, Release 5.4.1 git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks available from within JavaScript. 3. Commit and tag the release with the current version number: 133 Jupyter Notebook Documentation, Release 5.5.0 git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks sion available from within JavaScript. 3. Commit and tag the release with the current version number: 69 Jupyter Notebook Documentation, Release 5.4.0 git commit -am "release $VERSION" git tag $VERSION

FileContentsManager.post_save_hook runs on the filesystem path and model without content. This could be used to commit changes after every save, for instance. They are both called with keyword arguments: pre_save_hook(model=model want to automatically update dependencies and recompile JavaScript and CSS after checking out a new commit, you can install post-checkout and post-merge hooks which will do it for you: git-hooks/install-hooks sion available from within JavaScript. 3. Commit and tag the release with the current version number: 69 Jupyter Notebook Documentation, Release 5.3.1 git commit -am "release $VERSION" git tag $VERSION