In case you are not familiar with it, a pull-request is a notification of a change (or a bunch of changes) made by someone for one of your GitHub repositories. You can either accept them and merge them into your repository, or you can reject them, or something in-between. For example you can add comments to it and as the author of those changes to make further adjustments before you can merge the changes.

In this case the change was really simple.

This line

$pod =~ s(^$PodDir/)();

was replaced by this line:

$pod =~ s(^\Q$PodDir\E/)();

The problem was that the $PodDir could contain characters that would be interpreted by the regex engine as special characters even though what we wanted was exact matchig. Specifically there was a sequence of characters starting with a back-slash (\) character that looked like a Unicode property definition but that was invalid. See the error report.

The \Q character tells the regex engine to treat every character in the regex as regular character with no special meaning from that point till the end of the regex or till it encounters \E. So as far as I know the \E at the end was not required for this solution, but being explicit with it makes the code clearer.

Accepting the Pull-request

I got an e-mail notification about the Pull-request with a link. Following that link I could easily see the changes Sinan made. As I have Travis-CI on this repository, I could also see that not test was broken by this change. At least not on Linux. With the click of a button on the GitHub UI, I could merge the pull-request.

The original commit by Sinan.

The commit merging his changes.