What is git-upstream?
git-upstream is an open source Python application that can be used to keep in sync with upstream open source projects, mainly OpenStack.
The main usecase for this tool is for people who are doing active contributions to repositories that are mirrors of OpenStack repositories, with the intention that most of those contributions will be submitted to review.openstack.org at some point. If you are running a public cloud based on OpenStack, having local changes needed to use it in your environment, you can use git-upstream to stay up to date with the upstream master in a easier way (with respect to using raw git commands).
git-upstream provides new git subcommands to support rebasing of local-carried patches on top of upstream repositories. It provides commands to ease the use of git for who needs to integrate big upstream projects in their environment. The operations are performed using Git commands.
See also README.md, and USAGE.md files.
What git-upstream is not
The name of this tool includes the “git-” prefix because of the Git naming convention that a Git subcommand must have. So, as git-review (usually invoked with “git review […]”), this tool can be invoked using “git upstream […]”. That said, and even if git-upstream currently uses Change-Ids, it is not strictly related to git-review. In other words, git-review can (and most of the time will) be used without even knowing about git-upstream existence.
How can I contribute to git-upstream?
Git-upstream is in OpenStack:
As for any other OpenStack project, contributions are submitted thru the Gerrit review system.
To summarise:
create a Gerrit account (that is, a launchpad identity)
click on the “Sign in” link in the upper right corner here: https://review.openstack.org
install git-review
pip install git-review
clone the repo
setup to work with Gerrit
cd git-upstream git review -s
git-review will ask the username to use to submit changes to review.openstack.org, just enter the name you have registered in 1)
add cool features or fix nasty bugs
create your commit as usual
git add/rm <…> git commit
submit the change for review
git review
That’s it. You can see your change signing in to your review.openstack.org account.
Hold on tight, someone will come in shortly and will review your change! Meanwhile, you can join the OpenStack community on IRC. There is also a specific channel for git-upstream:
#git-upstream
If you need help, please join us on IRC!
Before writing new code, it is always a good idea to check if the required change is already in Gerrit:
https://review.openstack.org/#/q/project:openstack/git-upstream,n,z
More info about OpenStack and the Gerrit review process.
https://wiki.openstack.org/wiki/IRC http://www.mediawiki.org/wiki/Gerrit/git-review http://docs.openstack.org/infra/manual/developers.html http://docs.openstack.org/infra/manual/developers.html#development-workflow https://review.openstack.org/#/q/status:open,n,z
Metadata
Release files for git-upstream 0.12.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 | |
|---|---|---|---|---|
| git-upstream-0.12.1.tar.gz | 81.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_upstream-0.12.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 197.9 kB
Release files / git-upstream-0.12.1.tar.gz
| Download URL | git-upstream-0.12.1.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0b91882be0330eb8a8713f5cf8d9ea956165069a4125e600853b2bc1fa3b62e
|
|
BLAKE2b-256 checksum How to use checksums |
61cc139a19e5a9da62a6efa179cee96412a83f7b20f6c80a0de50709a105b252
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / git_upstream-0.12.1-py2-none-any.whl
| Download URL | git_upstream-0.12.1-py2-none-any.whl |
|---|---|
| Size | 116.2 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
013257cdd38c2ea794c64334790f09ca77f8324caeaf898e81982c1cf897ac2c
|
|
BLAKE2b-256 checksum How to use checksums |
8631018f96258c6969d6b96d9d7832e8a4e7c46e656ab3d9dc4749e007af57b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-upstream 0.12.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.