-
Notifications
You must be signed in to change notification settings - Fork 17.1k
Expand file tree
/
Copy path.asf.yaml
More file actions
145 lines (137 loc) · 5 KB
/
.asf.yaml
File metadata and controls
145 lines (137 loc) · 5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
# `.asf.yaml` is a branch-specific YAML configuration file for Git repositories to control features
# such as notifications, GitHub settings, etc.
# See its documentation for details: https://github.com/apache/infrastructure-asfyaml
---
#
# Additional non-standard features
#
meta:
environments:
- github_rulesets
github:
description: "Apache Airflow - A platform to programmatically author, schedule, and monitor workflows"
homepage: https://airflow.apache.org/
# Social media preview image is not supported by GitHub API/asf.yaml, need to be uploaded
# manually in GitHub repository --> Settings --> click "Edit" in "Social preview"
# See also:
# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview
# social_media_preview: docs/apache-airflow/img/logos/github_repository_social_image.png
labels:
# Note that GitHub only supports <=20 labels/topics per repo! Pipeline will fail if you add more.
- airflow
- apache
- apache-airflow
- automation
- dag
- data-engineering
- data-integration
- data-orchestrator
- data-pipelines
- data-science
- elt
- etl
- machine-learning
- mlops
- orchestration
- python
- scheduler
- workflow
- workflow-engine
- workflow-orchestration
features:
# Enable issues management
issues: true
# Enable projects for project management boards
projects: true
# Enable wiki for documentation
wiki: false
# Enable discussions
discussions: true
enabled_merge_buttons:
squash: true
merge: false
rebase: false
pull_requests:
# allow auto-merge
allow_auto_merge: false
# enable updating head branches of pull requests
allow_update_branch: true
# auto-delete head branches after being merged
del_branch_on_merge: true
# Legacy branch protection is being migrated to Rulesets below.
#
# `main` keeps the proven configuration here until the new ruleset is validated on other
# branches. We cannot test the new ruleset on `main` itself: ruleset settings are only applied
# from the default branch, so a broken config there would block fixing this file.
#
# Once the new ruleset is validated, `main` should be moved under the ruleset
# and removed from the legacy `protected_branches` section.
# This section should be kept empty to properly delete the legacy branch protection rules that
# are currently in place:
#
# protected_branches: ~
protected_branches:
main:
required_pull_request_reviews:
required_approving_review_count: 1
required_linear_history: true
required_conversation_resolution: true
required_signatures: false
rulesets:
- name: "Branch protection"
type: branch
branches:
includes:
# `main` stays under `protected_branches` above until this ruleset is validated on the
# branches below. We cannot test the new ruleset on `main` itself: ruleset settings are
# only applied from the default branch, so a broken config there would block fixing
# this file.
#
# Uncomment once the configuration is proven on the other branches.
# - "~DEFAULT_BRANCH"
- "v*-stable"
- "providers-fab/v*"
- "airflow-ctl/v*-stable"
- "chart/v*-stable"
required_pull_request_reviews:
required_approving_review_count: 1
required_linear_history: true
required_conversation_resolution: true
required_signatures: false
collaborators:
# Max 10 collaborators allowed
# https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#assigning-the-github-triage-role-to-external-collaborators
# Procedure for adding new member is listed in
# https://github.com/apache/airflow/blob/main/ISSUE_TRIAGE_PROCESS.rst#L97
- aritra24
- omkar-foss
- nathadfield
- sunank200
- cmarteepants
- karenbraganz
- gyli
- jroachgolf84
- Dev-iL
- kacpermuda
notifications:
jobs: jobs@airflow.apache.org
commits: commits@airflow.apache.org
issues: commits@airflow.apache.org
pullrequests: commits@airflow.apache.org
discussions: commits@airflow.apache.org