Add .hacktron/config.yaml#3
Open
hacktron-app[bot] wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR adds a
.hacktron/config.yamlfile to preserve this repo's current Hacktron PR branch scan settings and support the upcoming cutover to config-based repo configuration.Hacktron is changing how branch scan settings are configured:
.hacktron/config.yamlfile.This change is not live yet, so merging this PR should not affect current scanning behavior immediately. Once the cutover happens, this config will ensure the repo continues using its existing branch selection.
Changes
.hacktron/config.yamlNotes
This repo-level config file also lays the groundwork for more granular repo-specific controls in the future, such as labels and authors.
We'd appreciate it if you could make this change within the next week, by Wednesday, 15 July.
We'll also be reaching out via email and Slack, if you've connected with us there. Please let us know if you have any questions.