Skip to content
Code Formatting Lint

not tagging correctly fix #50

Sign in to view logs

not tagging correctly fix

not tagging correctly fix #50

Triggered via push June 11, 2024 12:11
@woensug-choiwoensug-choi
pushed 5972ff2
ros2
Status Success
Total duration 34s
Artifacts –

lint.yml

on: push
Run Linters for Code Format Check
23s
Run Linters for Code Format Check
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
Run Linters for Code Format Check
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
Run Linters for Code Format Check
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
Run Linters for Code Format Check
Received status code 403. Resource not accessible by integration https://docs.github.com/rest/checks/runs#create-a-check-run
Run Linters for Code Format Check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v1, wearerequired/lint-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run Linters for Code Format Check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run Linters for Code Format Check
Some check runs could not be created.
Run Linters for Code Format Check: .github/workflows/jazzy-source-build.yml#L69
69:101 [line-length] line too long (115 > 100 characters)