git merge pristine --no-commit
# resolve conflicts
git commit -asm "$APPLICATION $VERSION-scripts"
+ git tag $APP-$VERSION
.. note::
for matching. Then amend your commit and push back::
git commit --amend -a
- git push --force
+ git tag $APP-$VERSION-scripts
+ git push --force --tags
+
+On any other copies that have the older commit, run the following commands
+while on the ``master`` branch to grab the new version::
+
+ git fetch --tags $REMOTE
+ git reset --hard $REMOTE/master
+
+Be sure to verify that your commit is the correct one; you can check with
+``git show``, which should show the changes you made when amending the
+commit. Be especially careful to make sure you don't nuke any in
+configuration scripts changes.
Troubleshooting
---------------
'WIZARD_DBNAME': 'DB_NAME',
'WIZARD_DBUSER': 'DB_USER',
'WIZARD_DBPASSWORD': 'DB_PASSWORD',
+ 'WIZARD_SECRETKEY': 'SECRET_KEY',
})
# XXX: I have omitted an implementation for table prefix, on grounds that we
# do not permit it to be configured. If we do end up growing support for
raise Exception("Unversioned files exist, refusing to remove (override with --force)")
try:
sh.call("git", "rev-parse", "HEAD")
- _, _, ref = open(".git/HEAD").read().partition(' ')
+ _, _, ref = open(".git/HEAD").read().rstrip().partition(' ')
if not options.force:
if ref != "refs/heads/pristine" and os.path.exists(os.path.join(".git", ref)):
raise Exception("Not on pristine branch (override with --force)")