Skip to content

feat: Semantic Release workflow for Jeedom Plugins #7

feat: Semantic Release workflow for Jeedom Plugins

feat: Semantic Release workflow for Jeedom Plugins #7

Triggered via pull request November 26, 2023 17:32
Status Success
Total duration 35s
Artifacts

work.yml

on: pull_request
codeLintGlobal  /  Test Linters
14s
codeLintGlobal / Test Linters
php73  /  Run linters
14s
php73 / Run linters
php74  /  Run linters
10s
php74 / Run linters
php  /  phpcs
24s
php / phpcs
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
codeLintGlobal / Test Linters
This action does not have permission to create annotations on forks. You may want to run it only on `pull_request_target` events with checks permissions set to write. See https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#permissions for details.
codeLintGlobal / Test Linters
This action does not have permission to push to forks. You may want to run it only on `push` events.
codeLintGlobal / Test Linters
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
codeLintGlobal / Test Linters
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
codeLintGlobal / Test Linters
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
codeLintGlobal / Test Linters
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
codeLintGlobal / Test Linters
Some check runs could not be created.
php / phpcs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/