Behavior when using tree_dir is confusing
Bug #1247920 reported by
dobey
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tarmac |
Fix Released
|
High
|
dobey | ||
Bug Description
Tarmac allows specifying tree_dir to use a pre-existing dir to avoid creating a new branch every time. However, if one uses this, and creates the branch manually, without the correct options to bzr, one can end up with a local tree which can be committed to, but the changes will not get pushed to Launchpad, as the local tree is not a lightweight checkout.
Related branches
lp:~dobey/tarmac/lw-co-only
- Mike McCracken: Approve
-
Diff: 194 lines (+89/-29)4 files modifiedtarmac/bin/commands.py (+33/-25)
tarmac/branch.py (+15/-1)
tarmac/exceptions.py (+4/-0)
tarmac/tests/test_commands.py (+37/-3)
| Changed in tarmac: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
