Upload ESLint results to code scanning #3709
Conversation
|
Did I mess something up? Why did only 3 jobs run? Regardless, I want to make sure alerts and fixes are appearing correctly before I merge this. |
aeisenberg
force-pushed
the
aeisenberg/eslint-sarif
branch
3 times, most recently
from
50ddee9 to
4ca0e15
Compare
aeisenberg
force-pushed
the
aeisenberg/eslint-sarif
branch
from
4ca0e15 to
386679a
Compare
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
Thanks, @Daverlo. Working now. |
aeisenberg
force-pushed
the
aeisenberg/eslint-sarif
branch
from
af04b3e to
0a90b45
Compare
|
@charisk, would you mind taking another look at this? I've made some changes and you can see autofixes are appearing. I rebased in order to remove the intentional linting errors. |
Minor change to CI to ensure our SARIF is uploaded to code scanning.