fix: bulk create on mysql (#303) #1247
Annotations
6 warnings and 9 notices
tests (ubuntu-20.04, 3.8, pii_check)
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/
|
tests (ubuntu-20.04, 3.8, pii_check)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
tests (ubuntu-20.04, 3.8, quality)
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/
|
tests (ubuntu-20.04, 3.8, quality)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
tests (ubuntu-20.04, 3.8, django42)
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/
|
tests (ubuntu-20.04, 3.8, django42)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
tests (ubuntu-20.04, 3.8, django42)
Starting action
|
tests (ubuntu-20.04, 3.8, django42)
HTTP Request: GET https://api.github.com/repos/edx/edx-exams "HTTP/1.1 200 OK"
|
tests (ubuntu-20.04, 3.8, django42)
Computing coverage files & badge
|
tests (ubuntu-20.04, 3.8, django42)
HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=99%25&color=brightgreen "HTTP/1.1 200 OK"
|
tests (ubuntu-20.04, 3.8, django42)
Generating HTML coverage report
|
tests (ubuntu-20.04, 3.8, django42)
Saving coverage files
|
tests (ubuntu-20.04, 3.8, django42)
Files saved
|
tests (ubuntu-20.04, 3.8, django42)
You can browse the full coverage report at:
https://htmlpreview.github.io/?https://github.com/edx/edx-exams/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/edx/edx-exams/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/edx/edx-exams/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%2Fedx%2Fedx-exams%2Fpython-coverage-comment-action-data%2Fendpoint.json
See more details and ready-to-copy-paste-markdown at:
https://github.com/edx/edx-exams/tree/python-coverage-comment-action-data
|
tests (ubuntu-20.04, 3.8, django42)
Ending action
|