False warning for commit merged pr #1624

Activity

1. aibaars commented on Mar 29, 2023

   

   aibaars

   on Mar 29, 2023

   Contributor

   More actions

   Thanks for reporting this. The warning is obsolete these days and #1625 should stop it from being reported.

   In the past, CodeScanning compared the alerts found on a pull request branch to the alerts found previously on the "base" branch (a baseline) to determine which alerts were introduced by the pull request, which alerts were already present, and which alerts were fixed as a result of the pull request. If you had restrictions on the on.push trigger then it was more likely that the baseline for comparison is outdated or even missing.

   Recently, CodeScanning switched to simpler strategy for determining which alerts to display in a pull request. The new strategy no longer relies on a baseline, so the warning has become obsolete.

   👍React with 👍1Reacted by AnnAngela
2. AnnAngela commented on Mar 29, 2023

   

   AnnAngela

   on Mar 29, 2023

   Author

   More actions

   Thanks for reporting this. The warning is obsolete these days and #1625 should stop it from being reported.

   In the past, CodeScanning compared the alerts found on a pull request branch to the alerts found previously on the "base" branch (a baseline) to determine which alerts were introduced by the pull request, which alerts were already present, and which alerts were fixed as a result of the pull request. If you had restrictions on the on.push trigger then it was more likely that the baseline for comparison is outdated or even missing.

   Recently, CodeScanning switched to simpler strategy for determining which alerts to display in a pull request. The new strategy no longer relies on a baseline, so the warning has become obsolete.

   THX A LOT!
3. AnnAngela

   closed this as completedon Mar 29, 2023