git-open
Open a git repo in the browser from the terminal.
Features
From the terminal type the following command to open the current repository in your browser.
Usage
$ git-open --help
Usage: git-open [OPTIONS] COMMAND [ARGS]...
Open a git repo in the browser from the terminal.
Running the command without any sub-command will open the main page of the
repository.
Options:
--help Show this message and exit.
Commands:
branch Open the current branch
commit Open the current commit
compare Open a compare view
version Show the current git-open version
Installation
Using pip
pip install git-open
Using pipx (recommended)
pipx is a great tool to install python tools globally.
Installing pipx on macOS:
brew install pipx
pipx ensurepath
Installing git-open using pipx:
pipx install git-open
Credits
This package was initially created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
License
GNU General Public License v3.0
See LICENSE to see the full text.
Changelog
unreleased
v2.0.0
- Bumps all dependencies, including
sh1.x -> 2.x andclick8.0 -> 8.4 - Drops the
sixdependency - Requires Python 3.10 or later
- Fixes invalid regex escape sequences that warned on Python 3.12+
v1.3.0
- Adds the
actionscommand
v1.2.2
- Bumps dependencies
- Fixes the issue with
git+ssh://in remotes https://github.com/cfarvidson/git-open/pull/267
v1.2.1
- Bumps dependencies
v1.2.0
- Adds "git open compare" command
v1.1.2
- Upgraded dependencies
v1.1.1
- Fixes a bug when custom ports are used in the remote
v1.1.0
- Upgraded dependencies
- Updated readme to recommend the use of pipx over pipsi
- Adds a "git open commit" sub-command
- Adds a "git open branch" sub-command
v1.0.8
- Updated dependencies
v1.0.7
- Updated dependencies
- Moves to the new repository
v1.0.6
- Updated dependencies
v1.0.5
- Deploy to pypi from travis
v1.0.4
- Add a download badge from http://pepy.tech/project/git-open to the readme
- Add a test that will ensure that the dependencies will be checked by snyk.io when versions are bumped by dependabot
- Fixes an issue with opening public repositories
v1.0.3
- Fix the build
v1.0.2
- Fix the manifest.in
v1.0.1
- Add a vulnerabilities checking to the CI pipeline (snyk.io)
v1.0.0
- Add the package to pypi
- Update the install readme
v0.0.3
- Updated ci pipeline
v0.0.2
- Update the install description
v0.0.1
- Implemented tox testing
- Created
Metadata
Release files for git-open 2.0.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 | Provenance | Actions |
|---|---|---|---|---|
| git_open-2.0.0.tar.gz | 28.4 kB | Without provenance | Details for git_open-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_open-2.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for git_open-2.0.0-py2.py3-none-any.whl |
Total release size: 46.4 kB
Release files / git_open-2.0.0.tar.gz
| Download URL | git_open-2.0.0.tar.gz |
|---|---|
| Size | 28.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa13871c48899c58441368c6d913fc62b26f4737df0459fb6b7fb8f47a90ff4a
|
|
BLAKE2b-256 checksum How to use checksums |
bae734af2d15b75572464b8f303b008db7db515b31860833440371d05a651490
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / git_open-2.0.0-py2.py3-none-any.whl
| Download URL | git_open-2.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a4142b51f0c6b5a774fb0e91b38f0fc3aa58c3fb0b55521eef772dc3843279b8
|
|
BLAKE2b-256 checksum How to use checksums |
ce1622280b29a446df73c25e57a985804c6c8ee18312ac66e540c5ac35be59b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for git-open 2.0.0
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.