Sqitch manages changes and dependencies via a plan file, employing a
Merkle
tree pattern similar to
Git and
Blockchain to ensure deployment integrity.
As such, there is no need to number your changes, although you can if you want.
Sqitch doesn’t much care how you name your changes.
If you want to change selection, open document below and click on "Move attachment"
About Sqitchependencies on other changes — even changes from other Sqitch projects. This ensures proper order of execution, even when you’ve committed changes to your VCS out-of-order. Deployment integrity <span>Sqitch manages changes and dependencies via a plan file, employing a Merkle tree pattern similar to Git and Blockchain to ensure deployment integrity. As such, there is no need to number your changes, although you can if you want. Sqitch doesn’t much care how you name your changes. Iterative development Up until you tag and release your application, you can modify your change deployment scripts as often as you like. They’re not locked in just because they’ve been Summary
| status | not read | | reprioritisations | |
|---|
| last reprioritisation on | | | suggested re-reading day | |
|---|
| started reading on | | | finished reading on | |
|---|
Details