@rushton3179 Apologies, just got down to the PR in my inbox. For some reason this PR includes a bunch of commits from DKWoods that are already merged. I think you need to rebase your feature/hyperlink-tdd branch onto the latest master. Don't create a new branch, that would break the link to this PR. (Also, don't merge, python-docx doesn't have any merges, it uses a straight-line commit history :)

Hi @scanny, this branch is a nightmare to get a clean reset at the current release of v0.8.6. I cannot seem to get the changes by DKWoods to disappear. I want to start a new branch from v0.8.6, start again with a new PR, and get your ok at each step so it is clean.

The only unfortunate thing would be the loss of git commit records. I want to use the analysis done in the feature/hyperlink branch on the main repo and if I just copy paste the file these will be lost. Rebasing is just not cleaning up the history the way I would like though.

I will await your approval before I proceed. Also sorry it has been a while, I have been busy with studies and a new job dev job. Most of the code is just sitting here though so I would like to get it in.

Cheers.

Edit: Unmerged commits prior to v0.8.6 by DKWoods, not just commits :)

I have no idea why this merged and closed, I never did this. I can only assume its when I started resetting my branch to get back to just the analysis. In any case here is the new PR I have started and will do one piece at a time to ensure a cleaner commit history, #414.