...
|
...
|
@@ -11,11 +11,20 @@ in progress, details pending
|
11
|
11
|
work. Playbooks that depended on the former behaviour simply to add
|
12
|
12
|
force=True to the task that needs it. Affected modules:
|
13
|
13
|
|
|
14
|
+ * bzr: When local modifications exist in a checkout, the bzr module used to
|
|
15
|
+ default to temoving the modifications on any operation. Now the module
|
|
16
|
+ will not remove the modifications unless force=yes is specified.
|
|
17
|
+ Operations that depend on a clean working tree may fail unless force=yes is
|
|
18
|
+ added.
|
|
19
|
+ * git: When local modifications exist in a checkout, the git module will now
|
|
20
|
+ fail unless force is explictly specified. Specifying force will allow the
|
|
21
|
+ module to revert and overwrite local modifications to make git actions
|
|
22
|
+ succeed.
|
|
23
|
+ * hg: When local modifications exist in a checkout, the hg module used to
|
|
24
|
+ default to removing the modifications on any operation. Now the module
|
|
25
|
+ will not remove the modifications unless force=yes is specified.
|
14
|
26
|
* subversion: When updating a checkout with local modifications, you now need
|
15
|
27
|
to add force so the module will revert the modifications before updating.
|
16
|
|
- * git: When local modifications exist to a checkout, the git module will now
|
17
|
|
- fail unless force is explictly specified. Specifying force will allow the
|
18
|
|
- module revert and overwrite local modifications to make git actions succeed.
|
19
|
28
|
|
20
|
29
|
## 1.8.1 "You Really Got Me" - Nov 26, 2014
|
21
|
30
|
|