GitHub integration for flox
flox automation for GitHub repository managmenet
Exposed variables
- github_clone_url - http checkout URL
- github_url - public URL of the repository
- github_ssh_url - checkout URL used for git+ssh protocol
- github_repository - repository object as fetched from GitHub API
github_empty- True/False flaggit_repository- authenticated URL which can be used for all write operations
Installation
$ flox plugin install flox-github
or
$ pip install flox-github
Configuration
$ flox config --plugin github --scope=user
ℹ Starting configuration of github for 'user' scope
→ GitHub default organization [getflox]:
→ Default branch [develop]:
→ Enable vulnerability alerts [Y/n]:
→ Enable automated security fixes [Y/n]:
ℹ 'List of protected branches' configuration is accepting multiple values, each in new line, enter empty value to end input, '-' to delete value
→ List of protected branches [master]:
→ Create repository as private [Y/n]:
→ Enable projects [Y/n]:
→ Enable issue management [Y/n]:
→ Enable wiki [Y/n]:
ℹ 'Collaborators with "pull" permission' configuration is accepting multiple values, each in new line, enter empty value to end input, '-' to delete value
ℹ 'Collaborators with "push" permission' configuration is accepting multiple values, each in new line, enter empty value to end input, '-' to delete value
ℹ 'Collaborators with "admin" permission' configuration is accepting multiple values, each in new line, enter empty value to end input, '-' to delete value
New configuration:
Key Old value New value
─────────────────────────────────────────────────────────────
Collaborators with "pull" permission {} -
Collaborators with "push" permission {} -
Collaborators with "admin" permission {} -
Save plugin settings? [y/N]: y
ℹ Configuration saved: /Users/user/.flox/settings.toml
→ GitHub Access Token [xxx]: ------
New configuration:
Key Old value New value
──────────────────────────────────────────────────────────────────────────────────────────────────────────
GitHub Access Token ----- --------
Save plugin settings? [y/N]: y
ℹ Updated 1 secrets
Metadata
Release files for flox-github 0.2.1
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 | |
|---|---|---|---|---|
| flox-github-0.2.1.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flox_github-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 kB
Release files / flox-github-0.2.1.tar.gz
| Download URL | flox-github-0.2.1.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
517c90955deee53cad2a13d241f62f36edad914908a10bffd3b1f8e8d1432652
|
|
BLAKE2b-256 checksum How to use checksums |
2a4e5f39095b6f19eb2b55b40cca97321793b94fab8057acc839f3babd035d77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0 CPython/3.8.12 Linux/5.11.0-1025-azure
|
Release files / flox_github-0.2.1-py3-none-any.whl
| Download URL | flox_github-0.2.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fde87106ae7396195418073ac22931dd6c8c2abbe48c4204cef1ded15470d191
|
|
BLAKE2b-256 checksum How to use checksums |
031186a65ce7e22911c14483d508aa4681e23b4b2127414a261bb2e491755d17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0 CPython/3.8.12 Linux/5.11.0-1025-azure
|
Security for flox-github 0.2.1
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.