Repository navigation
Add .asf.yaml with baseline repository configuration - #4
Merged
Merged
Conversation
Contributor
|
Thank you - and yes, please start the conversations on dev@ list. |
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.
What
Adds a
.asf.yamlso the project can self-manage its GitHub repository settings through ASF Infra automation, per the ASF Infra .asf.yaml documentation.This PR intentionally covers only the baseline:
mergeandrebasedisabled) to keep a linear history.main(blocks force pushes and branch deletion).The file carries the standard ASF license header, so
mvn verify(RAT) passes without adding an exclusion.Out of scope — needs community discussion
Deliberately not configured yet; each deserves its own thread before we commit:
required_status_checks/required_pull_request_reviewsonmainHappy to follow up once those are agreed on the dev list.