This repository was archived by the owner on Mar 11, 2025. It is now read-only.
feat: check hashi message #48
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mpetrun5
requested review from
tcar121293,
MakMuftic and
nmlinaric
as code owners
|
Go Test coverage is 94.0 %\ ✨ ✨ ✨ |
|
Go Test coverage is 94.0 %\ ✨ ✨ ✨ |
nmlinaric
approved these changes
Sep 16, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fetch hashi message and if it exists submit the spectre proof on target domains.
Refactor step handler so it can support multiple source handlers that collects domains.
Related Issue Or Context
Closes: #47
How Has This Been Tested? Testing details.
Types of changes
Checklist: