Skip to content

Add .asf.yaml for repository configuration#3400

Open
deacon-mp wants to merge 1 commit into
apache:masterfrom
deacon-mp:chore/add-asf-yaml
Open

Add .asf.yaml for repository configuration#3400
deacon-mp wants to merge 1 commit into
apache:masterfrom
deacon-mp:chore/add-asf-yaml

Conversation

@deacon-mp

Copy link
Copy Markdown
Contributor

What

Adds .asf.yaml (currently absent from the repo) to configure this repository
through Apache Infrastructure's self-service mechanism.

Why

  • Notifications — routes GitHub commit/issue/PR activity to the archived ASF
    mailing lists so podling development is visible and archived on-list:
    • commit activity → commits@caldera.apache.org
    • issue & pull-request activity → dev@caldera.apache.org
  • Metadata / features — sets the description + homepage (caldera.apache.org),
    repo features, squash-only merges, delete-branch-on-merge, and Dependabot alerts.

For the PMC/IPMC to confirm

  • Issue/PR notifications go to dev@ (there is no dedicated notifications@/issues@
    list yet) — adjust if a separate list is preferred.
  • github.labels replaces the repo's GitHub topics wholesale; the set here is
    curated (dropped hacktoberfest/mitre-corporation) — adjust if any should stay.
  • Branch protection is included commented out — enable once required CI checks
    are agreed (needs the exact status-check context name).

The notifications: block only takes effect once this is merged to the default
branch (master).

Ref: https://infra.apache.org/asf-yaml.html

Route GitHub notifications to the archived ASF mailing lists and declare
repository metadata/features/merge policy via Apache Infrastructure's
.asf.yaml self-service mechanism (currently absent from the repo).

Notifications (effective on the default branch only):
  - commit activity      -> commits@caldera.apache.org
  - issue & PR activity   -> dev@caldera.apache.org

Also sets the description/homepage (caldera.apache.org), repo features,
squash-only merges, branch tidy-on-merge, and Dependabot alerts. Branch
protection is included as a commented template for the podling to enable.

Ref: https://infra.apache.org/asf-yaml.html
@pjfanning

pjfanning commented Jul 10, 2026

Copy link
Copy Markdown
Member

notifications@caldera.apache.org does exist - but it is up to you whether to use it. May not show up well in lists website because there are no emails for it display for this list.

Comment thread .asf.yaml

# --- OPTIONAL self-serve branch protection (enable once the project agrees on required checks) ----
# protected_branches:
# master:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should protect your main/master branch even if you don't configure status checks (yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants