René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Enable configuration to fail CI if new alerts are introduced","articleBody":"We are currently trying to migrate from LGTM to `codeql-action` due to [limitations in LGTM's infrastructure](https://github.community/t/lgtm-extraction-failure-for-c-asp-net-5-0-application/185834). \r\n\r\nWith LGTM, we could set it return a failing check any time new analysis alerts were introduced in an PR. This would allow us to prevent merging a PR if it introduced new alerts.\r\n\r\nWe set up the default GitHub Actions for `codeql-action` and it ran and found 6 alerts in our test suite, but the build did not put up a failing check that would have prevented merging.\r\n\r\nThis is our first PR that adds `codeql-action`, so perhaps this needs to be merged first so that future PRs have something to be compared against? We are hesitant to merge without knowing there is a way to configure the action to fail when new alerts are introduced.\r\n\r\n- PR: https://github.com/sillsdev/TheCombine/pull/1198\r\n- Scanning results: https://github.com/sillsdev/TheCombine/pull/1198/checks?check_run_id=2914899948\r\n- Alerts for PR: https://github.com/sillsdev/TheCombine/security/code-scanning?query=ref%3Arefs%2Fpull%2F1198%2Fmerge+tool%3ACodeQL","author":{"url":"https://github.com/johnthagen","@type":"Person","name":"johnthagen"},"datePublished":"2021-06-25T16:31:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/598/codeql-action/issues/598"}