From be9b4452453a293466dfefa89f2966a7d99f7598 Mon Sep 17 00:00:00 2001 From: Toshio Kuratomi Date: Thu, 29 Jan 2015 18:29:45 -0800 Subject: [PATCH] Document the force=no changes for version control modules --- CHANGELOG.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0d97ba5281d..57d855544de 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,11 +11,20 @@ in progress, details pending work. Playbooks that depended on the former behaviour simply to add force=True to the task that needs it. Affected modules: + * bzr: When local modifications exist in a checkout, the bzr module used to + default to temoving the modifications on any operation. Now the module + will not remove the modifications unless force=yes is specified. + Operations that depend on a clean working tree may fail unless force=yes is + added. + * git: When local modifications exist in a checkout, the git module will now + fail unless force is explictly specified. Specifying force will allow the + module to revert and overwrite local modifications to make git actions + succeed. + * hg: When local modifications exist in a checkout, the hg module used to + default to removing the modifications on any operation. Now the module + will not remove the modifications unless force=yes is specified. * subversion: When updating a checkout with local modifications, you now need to add force so the module will revert the modifications before updating. - * git: When local modifications exist to a checkout, the git module will now - fail unless force is explictly specified. Specifying force will allow the - module revert and overwrite local modifications to make git actions succeed. ## 1.8.1 "You Really Got Me" - Nov 26, 2014