Skip to content

fix: Support scraping pods metrics that is still in scheduling status and has no assigned node #394

fix: Support scraping pods metrics that is still in scheduling status and has no assigned node

fix: Support scraping pods metrics that is still in scheduling status and has no assigned node #394

Triggered via pull request October 11, 2023 05:58
@mickeyzzcmickeyzzc
edited #2217
Status Failure
Total duration 16s
Artifacts

semantic.yml

on: pull_request_target
Validate PR title for semantic commit message
5s
Validate PR title for semantic commit message
Fit to window
Zoom out
Zoom in

Annotations

1 error
Validate PR title for semantic commit message
No release type found in pull request title "Support scraping pods metrics that is still in scheduling status and has no assigned node". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit