Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/add-community-bundle.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

12 changes: 12 additions & 0 deletions .github/workflows/add-community-bundle.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,7 @@ safe-outputs:
add-labels:
allowed: [bundle-submission, validation-passed, validation-failed, needs-info]
max: 3
issue-intent: false
remove-labels:
allowed: [validation-passed, validation-failed, needs-info]

Expand Down Expand Up @@ -93,6 +94,17 @@ Community bundles are untrusted. Validate metadata and distribution evidence,
but do not claim to audit, endorse, or support bundle code or the components it
installs. Never register a submitted companion catalog automatically.

## Label Responsibilities

Applying the outcome labels is your responsibility, not a recommendation for a
maintainer. Use the `add_labels` safe output on source issue
#${{ github.event.issue.number }}, with plain strings in its `labels` array.
Never emit label objects with `suggest: true` or suggestion-only output.
For a Passed outcome, emit `labels: ["validation-passed"]`; for a Failed
outcome, emit `labels: ["validation-failed"]`. Follow the outcome rules below
for timing, stale-label removal, and Blocked validation; this requirement does
not turn environment blockers into submission failures.

## Triggering Conditions

This workflow is triggered by an `issues: labeled` event and is gated to the
Expand Down
Loading
Loading