Skip to main content

GitMiller

This description can be found on GitHub here

GitMiller is a tool for running Jupyter Notebooks from a (partial) Github repository. It downloads the repository in your temp folder, runs a designated notebook within it, and removes all downloaded files afterwards.

Installation

$ pip install gitmiller

After installation you can use the gitmiller command-line tool to run your github notebooks.

Usage

The command-line interface takes the following input parameters:

parameter description
-u, --username Username to gain access to GitHub repository
-p, --password Password Github repository
-t, --token Or use a Github token
-r, --repository URL of GitHub repository (can be a subfolder)
-n, --notebook filename of notebook you wish to execute, this file must exist in the root folder of the (partially) downloaded folder structure.
-o, --output local path where GitMiller will put the executed version of your notebook
-c, --config local path of YAML file in which you can add all mentioned paramaters

GitMiller uses Papermill to run your remote notebook. Besides executing, Papermill also enables you to parameterize notebooks. If you would like to override certain variables in your notebook, add the variables and values in the config YAML file under the papermill key. See example below.

This repository contains a folder example in which a notebook test.ipynb exists. If you would like to run this notebook with GitMiller, use either:

$ gitmiller -u <GITHUB USERNAME> -p <GITHUB PASSWORD>, -r https://github.com/UtrechtUniversity/GitMiller/tree/master/example, -n test.ipynb, -o <LOCAL OUTPUT-PATH>

or create the following YAML file:

repository: https://github.com/UtrechtUniversity/GitMiller/tree/master/example
username: <GITHUB USERNAME>
password: <GITHUB PASSWORD>
notebook: test.ipynb
output: <LOCAL OUTPUT-PATH>

papermill:
  a: 10
  b: 60

and run with:

$ gitmiller -c <PATH TO YAML-FILE>

Note for Windows users

The script isn't able to remove the temp-folder after the Notebook has been processed on Windows machines. I have tried a lot of things, but couldn't find a solution. Manually removing also turned out to be impossible when using a terminal. I give up. At the end a message is printed in which the path of the folder is mentioned so you can remove it yourself.

Metadata

Release files for gitmiller 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gitmiller 0.1.5
File Size Uploaded Provenance Actions
gitmiller-0.1.5.tar.gz 4.8 kB Without provenance Details for gitmiller-0.1.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for gitmiller 0.1.5
File Interpreter ABI Platform Actions
gitmiller-0.1.5-py3-none-any.whl Python 3 none any Details for gitmiller-0.1.5-py3-none-any.whl

Total release size: 10.1 kB

Release files / gitmiller-0.1.5.tar.gz

Download URL gitmiller-0.1.5.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
dad3d6fc633c34e550ef5656e8dc22b425729ded3933c7594f0c13dcd8eabe50
BLAKE2b-256 checksum
How to use checksums
d5d3b95f70790ac9e1fd2277fe6e2ea894fbe7ea7e4dc445b85e22ab0754bca0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/46.0.0.post20200309 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.7.6

Release files / gitmiller-0.1.5-py3-none-any.whl

Download URL gitmiller-0.1.5-py3-none-any.whl
Size 5.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e05b3160558e8bd887ca607d007715c2c9f32508227b977bb2fa50fff2cf2682
BLAKE2b-256 checksum
How to use checksums
70a2fa468a6997b7b739a42a2aedcf476cd4b347b5d2485a0944c6499fc9f0e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/46.0.0.post20200309 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.7.6

Security for gitmiller 0.1.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page