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/

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/

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/

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/

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/

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/

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/

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/

Starting action

HTTP Request: GET https://api.github.com/repos/edx/portal-designer "HTTP/1.1 200 OK"

Computing coverage files & badge

HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=86%25&color=orange "HTTP/1.1 200 OK"

Generating HTML coverage report

Saving coverage files

Files saved

You can browse the full coverage report at: https://htmlpreview.github.io/?https://github.com/edx/portal-designer/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/portal-designer/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/portal-designer/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%2Fportal-designer%2Fpython-coverage-comment-action-data%2Fendpoint.json See more details and ready-to-copy-paste-markdown at: https://github.com/edx/portal-designer/tree/python-coverage-comment-action-data