Git migrate
Execute commands from shell file, storing last successful execution in detached git branch.
How it works
You have some bash file(-s) with few commands inside. Each on it’s own line. If you will run it in shell – it will execute all of them.
During deploy you need to run only new commands, that was added to this file. Think of it as a one way DB migrations that will get commands to execute from git diff.
Git to the resque! System will store successfull commands executions in detached branch named .gitmigrate. Then if we will have 5 commands and only 3 of them was successful, on next run we will not run them.
Always run/include some code?
First lines until two new lines will be always executed. So when you have shebang and then 2 new lines (as it usual) – it will be executed. Also you can add some includes after your 1st line, that will allow you to have DSL-like functions inside your script. After which you shoudl have two new lines.
Conventions and configurations
Configuration values are in file .gitmigrate.
Configuration values with defaults
See .gitmigrate.dist as an example
Detached branch name _gitmigrate.
Path to command file(s) is .gitmigrate.*. It could be both .gitmigrate.sh or .gitmigrate.py or .gitmigrate.d/ directory.
1 maintainer
Metadata
1 maintainer
Release files for git-migrate 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 | |
|---|---|---|---|---|
| git-migrate-0.3.1.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_migrate-0.3.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 9.7 kB
Release files / git-migrate-0.3.1.tar.gz
| Download URL | git-migrate-0.3.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
499b94ed4b1d706392ecbf883ece85c22184401f4c6750feec8e8c9bfda92495
|
|
BLAKE2b-256 checksum How to use checksums |
02c1d4c367b20604a8d5e5204c574da11e6282971a310c0caffa704f0d8ee861
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / git_migrate-0.3.1-py2-none-any.whl
| Download URL | git_migrate-0.3.1-py2-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
e2de6689cc68a24db721aac35e6a419ff84334d588b621f2dbb5ca2cd2fa68b8
|
|
BLAKE2b-256 checksum How to use checksums |
1a7ed66dfc9549e3e0e2a644387b3cd140575f20a7979e4122db7d61c9db382c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-migrate 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.
