]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[workflow] Use MSVC problem matcher for Windows action build (GH-18532)
authorAmmar Askar <ammar@ammaraskar.com>
Mon, 28 Dec 2020 18:28:40 +0000 (13:28 -0500)
committerGitHub <noreply@github.com>
Mon, 28 Dec 2020 18:28:40 +0000 (12:28 -0600)
commit1031f23fc3aed6760785bf0f8290bd2b2cce41c2
tree9b2154c731f6d4288864baca4824fc1fb5f0111e
parentbf108bb21e1d75e30bd17141cc531dd08a5e5d0c
[workflow] Use MSVC problem matcher for Windows action build (GH-18532)

This makes warnings and errors from the compiler very prominent so this should help prevent warnings from sneaking into the code base and catch them in review. See https://discuss.python.org/t/using-github-problem-matchers-to-catch-warnings-early/4254 for more details

You can see a demo of this in action here: https://github.com/ammaraskar/cpython/pull/15/files#diff-9ba2eeca0f254ece0a9df4d7cb68e870

GCC and Sphinx matchers have previously been added in GH-18567 and GH-20325, respectively.
.github/problem-matchers/msvc.json [new file with mode: 0644]
.github/workflows/build.yml