Introduce .asf.yaml file #3020
Merged
Introduce .asf.yaml file #3020
Conversation
This file contains 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
rnewson
approved these changes
Jul 21, 2020
nickva
approved these changes
Jul 21, 2020
jjrodrig
approved these changes
Jul 22, 2020
dottorblaster
approved these changes
Jul 22, 2020
janl
approved these changes
Jul 22, 2020
Merged
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.
Overview
This introduces the
.asf.yamlfile, which gives us direct control over GitHub features we've previously had to ask ASF Infra to maintain for us.For now, this PR introduces only one specific change: it disables the ability to directly merge a PR with a branch. Instead, only the "squash" and "rebase" options will be allowed.
Because of this I am requesting 3 +1s from committers before I'll merge this change - though only a lazy majority is required.
Please see lines 29-32 of the file. We can also make this change if we want - which would send new/closed PR notifications to dev@, while sending all comments/etc to notifications@ as we do today.
Related Issues or Pull Requests
#2471