| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Merge release jobs into single workflow | Adam Janovsky | 2022-02-01 | 1 | -36/+0 |
| | | |||||
| * | GitHub actions: fine-tune PyPi action | Adam Janovsky | 2022-02-01 | 1 | -21/+14 |
| | | |||||
| * | Update python-publish.yml | Léo Vansimay | 2021-04-29 | 1 | -1/+11 |
| | | | | The method currently used only works when we tag a version number, I'm trying to use testpypi to avoid a failed build on each try. Moreover the build and push to PyPI will only trigger on a push with a tag | ||||
| * | add badges, workflow dispatch on publish | Adam Janovsky | 2021-04-24 | 1 | -20/+20 |
| | | |||||
| * | Update python-publish.yml | Léo Vansimay | 2021-04-23 | 1 | -1/+1 |
| | | | | Forcing 3.8 for compatibility purpose | ||||
| * | Update python-publish.yml | Léo Vansimay | 2021-04-21 | 1 | -1/+5 |
| | | | | The build seems to work well, modify the rules to publish the package when a push or PR on master occurs | ||||
| * | Update python-publish.yml | Léo Vansimay | 2021-04-19 | 1 | -3/+1 |
| | | | | calls the publisher on each push | ||||
| * | Create python-publish.yml | Léo Vansimay | 2021-04-16 | 1 | -0/+31 |
| Attempt to add a github action to publish a PyPI package on each release. | |||||
 |
index : sec-certs.git | |
| Tool for analysis of security certificates (Common Criteria, FIPS 140...). | crocs-muni |
| aboutsummaryrefslogtreecommitdiffhomepage |