Skip to content

use existing iptables APIs where possible #4331

use existing iptables APIs where possible

use existing iptables APIs where possible #4331

Triggered via pull request November 6, 2023 22:20
Status Success
Total duration 8m 58s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

linting.yml

on: pull_request
No "Apply suggestions from code review" Commits
6s
No "Apply suggestions from code review" Commits
Submariner K8s API Code Generation
4m 37s
Submariner K8s API Code Generation
Protobuf Code Generation
45s
Protobuf Code Generation
Commit Message(s)
8s
Commit Message(s)
Go
5m 16s
Go
Dependency Licenses
1m 57s
Dependency Licenses
Markdown Links (modified files)
12s
Markdown Links (modified files)
Markdown
10s
Markdown
Package Documentation
44s
Package Documentation
Shell
8s
Shell
Variant Analysis
3m 40s
Variant Analysis
Vulnerability Scanning
23s
Vulnerability Scanning
YAML
7s
YAML
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
No "Apply suggestions from code review" Commits
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Variant Analysis
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Variant Analysis
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.15.1.
Variant Analysis
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.