dzamir, 1 month ago

@dgregor79 @fabianfett @finestructure In this case there are two solutions:

1. history was important for the commits on this branch, so squash should not be used (or at least they should be squashed in a better way, by leaving this particular commit)
2. create another PR for the workaround and have it tracked as a different issue