Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: declare Channel explicitly #657

Merged
merged 2 commits into from
Apr 29, 2024
Merged

Conversation

fukusuket
Copy link
Collaborator

@fukusuket fukusuket commented Apr 28, 2024

What Changed

Fixed a rule where Channel was not specified.
When implementing Yamato-Security/hayabusa#1317 , the Channel must be specified explicitly.

Test

I confirmed that there is no difference in the number of detections before and after the modification as shown below.

after:
https://github.com/Yamato-Security/hayabusa-rules/actions/runs/8871225497/job/24353898756#step:5:4856

before:
https://github.com/Yamato-Security/hayabusa-rules/actions/runs/8871253258/job/24353962845#step:5:4856

I would appreciate it if you could review when you have time馃檹

@fukusuket fukusuket self-assigned this Apr 28, 2024
@fukusuket fukusuket added the bug Something isn't working label Apr 28, 2024
@fukusuket fukusuket marked this pull request as ready for review April 28, 2024 23:56
@fukusuket fukusuket changed the title fix: declare channel explicitly fix: declare Channel explicitly Apr 28, 2024
Copy link
Collaborator

@YamatoSecurity YamatoSecurity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fukusuket Thanks for fixing these! I am not sure why I wrote them this way... 馃槄

@YamatoSecurity YamatoSecurity merged commit 51d415a into main Apr 29, 2024
2 checks passed
@YamatoSecurity YamatoSecurity deleted the explicitly-declare-channel branch April 29, 2024 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants