Skip to content

Commit f8a6189

Browse files
ansnfernandpyansys-ci-botRobPasMue
authored
maint: check vulnerabilities action (#650)
Co-authored-by: pyansys-ci-bot <[email protected]> Co-authored-by: Roberto Pastor Muela <[email protected]>
1 parent 9f36fea commit f8a6189

File tree

11 files changed

+156
-138
lines changed

11 files changed

+156
-138
lines changed

.github/workflows/ci_cd.yml

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -191,4 +191,15 @@ jobs:
191191
with:
192192
token: ${{ secrets.PYANSYS_CI_BOT_TOKEN }}
193193
bot-user: ${{ secrets.PYANSYS_CI_BOT_USERNAME }}
194-
bot-email: ${{ secrets.PYANSYS_CI_BOT_EMAIL }}
194+
bot-email: ${{ secrets.PYANSYS_CI_BOT_EMAIL }}
195+
196+
check-vulnerabilities:
197+
name: "Check library vulnerabilities"
198+
runs-on: ubuntu-latest
199+
steps:
200+
- uses: ansys/actions/[email protected]
201+
with:
202+
python-version: ${{ env.MAIN_PYTHON_VERSION }}
203+
token: ${{ secrets.PYANSYS_CI_BOT_TOKEN }}
204+
python-package-name: ${{ env.PACKAGE_NAME }}
205+
dev-mode: ${{ github.ref != 'refs/heads/main' }}

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,3 +56,5 @@ doc/build/
5656

5757
doc/source/examples/gallery_examples/*
5858
doc/source/sg_execution_times.rst
59+
info_bandit.json
60+
info_safety.json

PULL_REQUEST_TEMPLATE.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,19 @@
55
**Please mention the issue number or describe the problem this pull request addresses.**
66

77
## Checklist:
8-
- [] Run unit tests and make sure they all pass
8+
- [ ] Run unit tests and make sure they all pass
99
- Run tests without Sherlock running
1010
- Run tests with Sherlock GRPC connection
11-
- [] Check and fix style errors
11+
- [ ] Check and fix style errors
1212
- pre-commit command line check
1313
- Problems tab in PyCharm
14-
- [] Bench test new/modified APIs by using and modifying the code in the example for the API method
15-
- [] Add new classes to rst files, located at: <pysherlock>\doc\source\api
16-
- [] Generate documentation
17-
- [] Verify the HTML. It gets generated at: <pysherlock>\doc\build\html.
14+
- [ ] Bench test new/modified APIs by using and modifying the code in the example for the API method
15+
- [ ] Add new classes to rst files, located at: <pysherlock>\doc\source\api
16+
- [ ] Generate documentation
17+
- [ ] Verify the HTML. It gets generated at: <pysherlock>\doc\build\html.
1818
- Open index.html
1919
- Click on "API Reference" at the top.
2020
- Verify HTML for API changes.
21-
- [] Check that test code coverage is at least 80% when Sherlock is running
22-
- [] Make sure that the title of the pull request follows [Commit naming conventions](https://dev.docs.pyansys.com/how-to/contributing.html#commit-naming-conventions) (e.g. ``feat: adding new PySherlock command``)
21+
- [ ] Check that test code coverage is at least 80% when Sherlock is running
22+
- [ ] Check vulnerabilities locally
23+
- [ ] Make sure that the title of the pull request follows [Commit naming conventions](https://dev.docs.pyansys.com/how-to/contributing.html#commit-naming-conventions) (e.g. ``feat: adding new PySherlock command``)
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Maint: check vulnerabilities action

0 commit comments

Comments
 (0)