Welcome to gitrecipe doc page
Usage
Recipe clones git repository and checkouts to revision, if it is provided in configuration. You can use recipe like this:
[buildout] parts = data [data] recipe = gitrecipe repository = git://example.com/my-git-repo.git rev = origin/redevlop-branch
Options
repository - repository url
ref of rev - git reference wich you want to checkout
Notes
rev option leaved for compatibility with zerokspot.recipe.git. It is better to use ref parameter, because it corresponds Git terminology
Since 0.0.2 recipe does check existing repository while install and update. Repository origin url must be the same as given in rev option. Otherwise repository will be deleted and cloned again.
About
I’ve used recipe zerokspot.recipe.git, but as for me, it too complex and has some disadvantages:
it does not allow commit from the source folder, default remote is local copy in downloads
it does not allow to specify the tag or branch of the repository, only revision hash
So I wrote my own git recipe with compatible options. You can choose this or that.
1 maintainer
Metadata
1 maintainer
Release files for gitrecipe 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 | |
|---|---|---|---|---|
| gitrecipe-0.0.2.tar.gz | 4.5 kB | Without provenance | Details |
Release files / gitrecipe-0.0.2.tar.gz
| Download URL | gitrecipe-0.0.2.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86530e16ab7d0501bb4eadc3e6e4b98ecffa777e0d26827734295b8aa87fbe5f
|
|
BLAKE2b-256 checksum How to use checksums |
c3a4f4a38183b614be7b49957d793726cab58d30d81d6a80bde63226a0cb185f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gitrecipe 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.
