=====================
Things you can do:
- Set commit status
- Create a pull request
- Merge a pull request
- Merge
Set Status on a commit:
Usage:
github-commit-status -c <commit-hash> -s <status> -u <github-username> -p <github-password> -r <github_repo> --url <URL> --context <context> -d "<description>"
github-commit-status -c <commit-hash> -s <status> -t <github-token> -r <github_repo> --url <URL> --context <context> -d "<description>"
Options:
-c <commit-hash>, --commit-hash <commit-hash> Github commit hash
-s <status>, --status <status> Status to set [pending, success, error, or failure]
-u <username>, --username <username> github username
-p <password>, --password <password> github password
-t <token>, --token <token> github access token
-r <repository>, --repo <repository> github repository
-d <description> --description <description> description of the status
--url <url> URL to refer back to
--context <context> The context of the status. Typically the name of the service creating the status.
Create a pull request:
Usage:
github-create-pull-request -h <head> -b <base> -t <token> -r <repo> [-d "<description>" --title <title>]
Options:
-h <head>, --head <head> Head: the branch you're pulling from.
-b <base>, --base <base> Base: the branch you're pulling to.
-t <token>, --token <token> github access token
-r <repository>, --repo <repository> github repository
-d <description> --description <description> The pull request description.
--title <title> The pull request title.
Merge a pull request:
Usage:
github-merge-pull-request (-h <head> -b <base> | -p <pull-number>) -t <token> -r <repo>
Options:
-h <head>, --head <head> Head: the branch you're pulling from.
-b <base>, --base <base> Base: the branch you're pulling to.
-t <token>, --token <token> github access token
-r <repository>, --repo <repository> github repository
-p <pull-number> --pull-number <pull-number> The pull request ID number.
Merge
Usage:
github-merge -h <head> -b <base> -t <token> -r <repo>
Options:
-h <head>, --head <head> Head: the branch you're pulling from.
-b <base>, --base <base> Base: the branch you're pulling to.
-t <token>, --token <token> github access token
-r <repository>, --repo <repository> github repository
See https://github.com/nricklin/githubtools
1 maintainer
Metadata
1 maintainer
Release files for githubtools 0.3.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 | |
|---|---|---|---|---|
| githubtools-0.3.1.tar.gz | 3.9 kB | Without provenance | Details |
Release files / githubtools-0.3.1.tar.gz
| Download URL | githubtools-0.3.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8601d0d994aa0ea7982d10ea4b26c95afee6540c39ab3a915ffa680c4f0abcb0
|
|
BLAKE2b-256 checksum How to use checksums |
71cf37c809a816e33639498888df2123dee31c4174d00763a5ae83d0a7c0980a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for githubtools 0.3.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.
