anchor.diff:  Generated files will be saved into `.release/` subdirectory. You can
   remove files you don't need anymore. You can re-generate files for any
   commit by running `git checkout <commit>; ./release`.
  +
  +NOTE: Re-generated files may differ from original ones, for ex. in case
  +different compiler was used or build date was embedded in generated files
  +or generated files was manually changed (this may happens in advanced
  +cases when you join two branches of project).
   
   === ./deploy
   
  
positive.code: executed by `./deploy` in deploy (`_live/`) directory.
  
  
  
negative.code: - convert data in database
  - restart background processes/services affected by these changes
  
  NOTE: When you're doing `git merge` or `git cherry-pick` you usually
  should not modify part of `migrate` files which was already included in
  previous releases - you can make changes only after latest `VERSION` line.
  This restriction doesn't apply to `git rebase` or in case when you're
  fixing wrong downgrade operations for already released version.
  
  You can run `./build` or `./build --test` at any time just to make sure
  your project builds ok and pass build-time tests.
  
  