forkyeah
The purpose of this project is to facilitate the management of forks of upstream repositories, where the fork is basically a tag or hash from upstream with a one or more patches applied to it. These patches may be stored locally, or fetched over the network for example using the diff link which GitHub supplies for each PR, or from a gist.
The configuration file is fork.yaml and looks like the following:
upstream:
repo: https://github.com/ros-controls/ros_control.git
ref: 0.13.0
fork:
repo: git@gitlab.yourcompany.com:forks/ros_control.git
branch: fork-latest
tag: fork-%Y%m%d-%H%M%S
apply:
- patch: https://github.com/ros-controls/ros_control/pull/301.diff
name: "Upstream PR 301: CompositeController template."
- patch: https://github.com/ros-controls/ros_control/commit/a65fb8cc.diff
name: "Revert a65fb8cc to resolve merge conflicts."
reverse: True
- patch: https://github.com/ros-controls/ros_control/pull/302.diff
name: "Upstream PR 302: Variadic Controller template."
- patch: http://gitlab.clearpathrobotics.com/snippets/72/raw
name: "Un-deprecate MultiInterfaceController."
The intention is that this fork.yaml config file is stored in an orphan branch
of the fork repo, and that that orphan branch is the default, so that when you
want to update it you simply make and commit changes (add, remove, reorder patches,
or change the version used as the starting point) and then rerun:
forkyeah
The tool will handle checking out the given baseline, switching to the fork-latest branch, applying the patches, creating a new tag according to the template, and pushing everything to the defined fork repo. '
Metadata
Release files for forkyeah 0.0.2
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 |
|---|---|---|---|---|
| forkyeah-0.0.2.tar.gz | 3.5 kB | Without provenance | Details for forkyeah-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| forkyeah-0.0.2-py2-none-any.whl | Python 2 | none | any | Details for forkyeah-0.0.2-py2-none-any.whl |
Total release size: 8.0 kB
Release files / forkyeah-0.0.2.tar.gz
| Download URL | forkyeah-0.0.2.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
092f483040f84f6e3f104898a1ed013e90787957b8e0c8547402642bd6479518
|
|
BLAKE2b-256 checksum How to use checksums |
e569774d1b91f46d0a5bd712ace30025f02495319f2dc8db2bfc906f22ea834f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / forkyeah-0.0.2-py2-none-any.whl
| Download URL | forkyeah-0.0.2-py2-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
4431cdfc06718be6273a680e59482b5676110bb5d5b0763af71386e1185cda15
|
|
BLAKE2b-256 checksum How to use checksums |
c1201cf0689d08f7b6dc687709c76e0e97c8ccf0d6c4010f44c05bb2de777016
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for forkyeah 0.0.2
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.