'bst workspace open -f' does not behave as documented

Summary

Steps to reproduce

1. Open a workspace for an element bst workspace open element.bst workspace_dir
2. Make a change to the source code checked out to workspace_dir
3. Close the workspace bst workspace close element.bst
4. force open a new workspace in the same directory at the previous on bst workspace open -f element.bst workspace_dir
5. Notice the changes made at step 2 will have persisted.

What is the current bug behavior?

If there is an existing workspace for element.bst in the directory workspace_dir which has been closed, using bst workspace open -f element.bst workspace_dir does not checkout an unmodified copy of the elements source code. I.e any changes previously make to the workspace checked out it workspace_dir persist, despite the force option.

What is the expected correct behavior?

Using bst workspace open -f element.bst workspace_dir should overwrite an existing workspace's contents with an unmodified copy of the element's source code.

Other relevant information

This was observed in version 1.1.3+171

---