issue-expander
Expand GitHub issue references into Markdown links
$ echo 'rust-lang/rust#106827' | issue-expander -
[Update LLVM to 15.0.7 #106827](https://github.com/rust-lang/rust/pull/106827)
$ echo '#106827' | issue-expander --default-source 'rust-lang/rust'
[Update LLVM to 15.0.7 #106827](https://github.com/rust-lang/rust/pull/106827)
This project is not yet stable in any way and makes absolutely no guarantees about behavior (between releases, or otherwise).
Usage
Usage: issue-expander [OPTIONS] FILE
Turn references like "foo/bar#123" into Markdown links, like
"[Prevent side fumbling #123](https://github.com/foo/bar/pull/123)"
issue-expander works for references to issues and to pull requests.
References are only expanded if they are found at GitHub. To expand
references from private repositories, you'll need to pass your GitHub token.
This can be done via environment variables or via command line options.
To interpret references like `#1138` as `adamwolf/issue-expander#1138`,
specify defaults using `--default-source`.
Options:
--default-source USER/REPO Use USER/REPO when not specified in issue
reference. (Example: "adamwolf/issue-expander")
-p, --github-token TOKEN GitHub token for looking up issue references. You
may want to use the environment variable
ISSUE_EXPANDER_GITHUB_TOKEN instead.
--version Show the version and exit.
--help Show this message and exit.
Installation
If you use Homebrew, you can install issue-expander like this:
brew tap adamwolf/issue-expander
brew install issue-expander
Otherwise, I recommend installing with pipx. Once you've got pipx installed, you can install issue-expander like this:
pipx install issue-expander
and pipx installs issue-expander into its own little area, just for you, where you don't have to worry about it messing with any system-wide or even user-wide Python dependencies.
If you want to generate a binary that can run issue-expander without needing Python to be installed, see BUILDING.md.
If you want to do something different, issue-expander is available on PyPI. Go hogwild.
Development
There are a lot of ways to set up a development environment for a Python application. This is one of them.
Before you follow these steps, make sure Python 3 is installed.
- Clone the issue-expander repository.
git clone https://github.com/adamwolf/issue-expander.git
- Create a virtual environment and activate it.
cd issue-expander
python3 -m venv venv
source venv/bin/activate
- Install the package in editable mode (with development extras).
pip install -e .[dev]
- Make sure you can run the tests.
pytest
- Make sure you can run the linter.
pre-commit run --all-files
At this point, you should be able to make changes to the code.
Contributing
See CONTRIBUTING.md.
Metadata
Release files for issue-expander 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| issue_expander-0.1.12.tar.gz | 6.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| issue_expander-0.1.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.2 kB
Release files / issue_expander-0.1.12.tar.gz
| Download URL | issue_expander-0.1.12.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
662087a679306983c33b5573e719f8bc353f2047c9b9125507ddc320953ab7f4
|
|
BLAKE2b-256 checksum How to use checksums |
8a6f94da18fe0ae64ac83a67a6dd784bb2eb849afcd94a8315f2a1e52c5c079b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / issue_expander-0.1.12-py3-none-any.whl
| Download URL | issue_expander-0.1.12-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e939f433509c3a9cc9e4544dab9d9878c605e131739f3811936e0c8fc78e9d33
|
|
BLAKE2b-256 checksum How to use checksums |
edd88ef688f1675d43fc83bf93f13765bde9bb964c9047c1a77f05180312910b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for issue-expander 0.1.12
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.