Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The recent merge of feature_exception into devel actually DELETED all of the changes in feature_exception. It looks like the merge commit only pulled in the change from the first commit to feature_exception, then the rest was removed.
(I recommend using "git pull origin branch" within a feature branch to pull in changes from other feature branches if merging multiple branches together, e.g.
then complete the pull request of feature_branch1 as it will merge in and close all of the other feature branches)
This couldn't be reverted, so I have manually restored feature_exception, then created feature_exception2 from devel, then copied across all of the changed files from feature_exception to feature_exception2. I then regenerated all of the Python wrappers.
I believe that all of the other merges are still preserved - the new mol/test_matcher.py test still exists and passes.
@lohedges - please check that I haven't trashed your changes.