Infra: Add community workflows, compliance automation, and dependency review#258
Infra: Add community workflows, compliance automation, and dependency review#258sfc-gh-swalia wants to merge 2 commits into
Conversation
|
@sfc-gh-swalia Thanks for that! I will do the review. I saw some changes that are not required now and also to be clarified for release. |
|
Can you please disclose any AI tool assistance? |
Hey @jbonofre - Yes - I used Claude Opus 4.6 assistance for this PR. Primarily used it for researching ASF compliance patterns across workflow infrastructure, drafting workflow YAML andd validating configurations. I reviewed and validated the code before committing. I propose we make AI tool disclosure a standard part of our contribution process i.e. a simple optional note in the PR template and a brief section in CONTRIBUTING.md. This keeps us transparent and aligned. Happy to include that in |
Summary
Adding community management workflows and compliance automation to bring GitHub infra in line with other ASF projects (modeled on Apache Iceberg's approach).
Compliance:
Community management:
needs-triagesync-labels(wildcard catch-all forconverters/**+ specific per-converter labels)awaiting-responseflips toneeds-reviewwhen author respondsawaiting-response, exempts anything assigned or milestoned)Governance:
Area: Description) for clean squash-merge historyAll workflows include the ASF license header and are guarded with
if: github.repository_owner == 'apache'so they do not fire on contributor forks.Note: The labels referenced by these workflows (
needs-triage,awaiting-response,needs-review,stale,converter/*, etc.) do not exist yet — GitHub creates them automatically on first use.Checklist
Compliance