Skip to content
Linting

Handle conflicting service ports when merging per MCS spec #2610

Sign in to view logs

Handle conflicting service ports when merging per MCS spec

Handle conflicting service ports when merging per MCS spec #2610

Triggered via pull request September 24, 2024 19:20
@tpantelistpantelis
synchronize #1645
tpantelis:port_merge
Status Success
Total duration 3m 29s
Artifacts –

linting.yml

on: pull_request
No "Apply suggestions from code review" Commits
2s
No "Apply suggestions from code review" Commits
Commit Message(s)
10s
Commit Message(s)
Go
2m 54s
Go
Dependency Licenses
3m 20s
Dependency Licenses
Markdown Links (modified files)
13s
Markdown Links (modified files)
Markdown
7s
Markdown
Package Documentation
28s
Package Documentation
Vulnerability Scanning
23s
Vulnerability Scanning
YAML
10s
YAML
Fit to window
Zoom out
Zoom in

Annotations

1 warning
No "Apply suggestions from code review" Commits
The following actions use a deprecated Node.js version and will be forced to run on node20: tim-actions/get-pr-commits@198af03565609bb4ed924d1260247b4881f09e7d, tim-actions/commit-message-checker-with-regex@094fc16ff83d04e2ec73edb5eaf6aa267db33791. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/