Skip to content

chore: use env_logger for debugging instead of println! #973

chore: use env_logger for debugging instead of println!

chore: use env_logger for debugging instead of println! #973

Triggered via pull request September 18, 2023 21:43
@meekteekmeekteek
opened #174
Status Failure
Total duration 28s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pr.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

1 error
Title
No release type found in pull request title "Use env_logger for debugging instead of println!". 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