Introduction
A simple python console script to let me convert GitHub Closed Issues output to Markdown.
Typically after working a multi-repository project I want to know the issues in each repository that have been fixed since the last release.
It produces output in the following format:
* [121](https://api.github.com/repos/hasii2011/pytrek/issues/121) Implement Move automatic
* [120](https://api.github.com/repos/hasii2011/pytrek/issues/120) Fixing of devices is not asynchronous
* [119](https://api.github.com/repos/hasii2011/pytrek/issues/119) We should only have a single Super Commander
Overview
The basic command structure is:
Usage: pygh2md [OPTIONS]
slug A repository slug in the format <user-name>/repository-name;
e.g., `hasii2011/TestRepository`
sinceDate The start date to query for closed issues; Format yyyy-mm-
dd; e.g., 2024-03-01
output_file The filename for the markdown output file
appends If `True` append this script's output (default is True)
Options:
--version Show the version and exit.
-s, --slug TEXT GitHub slugs to query [required]
-d, --since-date TEXT The date from which we want to start searching.
[required]
-o, --output-file TEXT The output markdown file. [required]
-a, --append Append to output file
--help Show this message and exit.
A simple example:
pygh2md -s hasii2011/pytrek -d 2024-06-01 -o PytrekClosedIssues.md
Installation
pip install pygh2md
Written by Humberto A. Sanchez II <mailto@humberto.a.sanchez.ii@gmail.com>, (C) 2024
Note
For all kind of problems, requests, enhancements, bug reports, etc., please drop me an e-mail.
I am concerned about GitHub's Copilot project
I urge you to read about the Give up GitHub campaign from the Software Freedom Conservancy.
While I do not advocate for all the issues listed there I do not like that a company like Microsoft may profit from open source projects.
I continue to use GitHub because it offers the services I need for free. But, I continue to monitor their terms of service.
Any use of this project's code by GitHub Copilot, past or present, is done without my permission. I do not consent to GitHub's use of this project's code in Copilot.
Metadata
Release files for pygh2md 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pygh2md-0.2.0.tar.gz | 19.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pygh2md-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.7 kB
Release files / pygh2md-0.2.0.tar.gz
| Download URL | pygh2md-0.2.0.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c20118548f4b06571fbc97ea91d2f1683cbaeb50db3bee4cc261069c89dc395c
|
|
BLAKE2b-256 checksum How to use checksums |
a81151cd6b152ab890e11192bbc6ada868518ea9b772b83922786cd7638814c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 31, 2025.
Transparency logRelease files / pygh2md-0.2.0-py3-none-any.whl
| Download URL | pygh2md-0.2.0-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dad6c4b55a5afea2fdac63b0936d0c2a7ff76b41d237ae94ba59bc73bd7ebfab
|
|
BLAKE2b-256 checksum How to use checksums |
c9727681565fb40a319173cd3b2c2f7cbc818aab3394cd42e944eda2dde6a835
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 31, 2025.
Transparency log