add coverage to workflow (#8) #189
Annotations
7 warnings and 10 notices
pytest 3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
pytest 3.9
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
pytest 3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
pytest 3.10
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
pytest 3.12
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
pytest 3.x
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Coverage
Starting action
|
Coverage
HTTP Request: GET https://api.github.com/repos/diceroll123/neofoodclub.py "HTTP/1.1 200 OK"
|
Coverage
Computing coverage files & badge
|
Coverage
HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=100%25&color=brightgreen "HTTP/1.1 200 OK"
|
Coverage
Generating HTML coverage report
|
Coverage
Creating branch python-coverage-comment-action-data
|
Coverage
Saving coverage files
|
Coverage
Files saved
|
Coverage
You can browse the full coverage report at:
https://htmlpreview.github.io/?https://github.com/diceroll123/neofoodclub.py/blob/python-coverage-comment-action-data/htmlcov/index.html
You can use the following URLs to display your badge:
- Badge SVG available at:
https://raw.githubusercontent.com/diceroll123/neofoodclub.py/python-coverage-comment-action-data/badge.svg
- Badge from shields endpoint is easier to customize but doesn't work with private repo:
https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/diceroll123/neofoodclub.py/python-coverage-comment-action-data/endpoint.json
- Badge from shields dynamic url (less useful but you never know):
https://img.shields.io/badge/dynamic/json?color=brightgreen&label=coverage&query=%24.message&url=https%3A%2F%2Fraw.githubusercontent.com%2Fdiceroll123%2Fneofoodclub.py%2Fpython-coverage-comment-action-data%2Fendpoint.json
See more details and ready-to-copy-paste-markdown at:
https://github.com/diceroll123/neofoodclub.py/tree/python-coverage-comment-action-data
|
Coverage
Ending action
|