Skip to content

docs: clarify maintainer applies submission label during triage - #4041

Merged
mnriem merged 1 commit into
github:mainfrom
mnriem:mnriem-docs-preset-submission-label
Aug 10, 2026
Merged

docs: clarify maintainer applies submission label during triage#4041
mnriem merged 1 commit into
github:mainfrom
mnriem:mnriem-docs-preset-submission-label

Conversation

@mnriem

@mnriem mnriem commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

Clarifies that community extension, preset, and bundle submissions are validated by label-triggered agentic workflows (add-community-*) that only run once the corresponding *-submission label is applied. On this public repository contributors cannot apply that label themselves, so a maintainer applies it during issue triage. This was previously undocumented, which led a contributor to ask maintainers to apply the label manually (see #4039).

Changes

  • Issue templates (preset_submission.yml, extension_submission.yml, bundle_submission.yml): add an "After submitting" note explaining a maintainer applies the *-submission label during issue triage to start validation, and that contributors do not need to apply or re-request it.
  • presets/PUBLISHING.md: add a callout in the Verification Process section.
  • extensions/EXTENSION-PUBLISHING-GUIDE.md: correct the inaccurate step that claimed issues are "automatically labeled and assigned" — they are not; a maintainer applies the label during triage.

Scope notes

  • Workflows use a PR-based submission model (workflows/PUBLISHING.md), not a label-triggered issue flow, so no change was needed there.
  • Workflow steps have no documented submission process at all; that is a separate, pre-existing gap and is intentionally out of scope for this PR.

Disclosure

Authored autonomously by GitHub Copilot (model: Claude Opus 4.8) on behalf of @mnriem. Changes are documentation-only.

Community extension, preset, and bundle submissions are validated by
label-triggered agentic workflows that only run once the corresponding
`*-submission` label is applied. On this public repo contributors cannot
apply that label themselves, so a maintainer applies it during issue
triage. Document this in the three submission issue templates, the preset
publishing guide, and correct the extension guide's inaccurate claim that
issues are "automatically labeled and assigned".

Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3b6f6854-9be6-4b67-b5b9-34b19ededcb8
Copilot AI balanced review requested due to automatic review settings August 10, 2026 20:37
@mnriem
mnriem merged commit c3bbcc4 into github:main Aug 10, 2026
13 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Clarifies that maintainers apply submission labels during triage to trigger automated catalog validation.

Changes:

  • Adds post-submission guidance to extension, preset, and bundle issue forms.
  • Corrects extension and preset publishing documentation.
Show a summary per file
File Description
.github/ISSUE_TEMPLATE/bundle_submission.yml Explains bundle label triage.
.github/ISSUE_TEMPLATE/extension_submission.yml Explains extension label triage.
.github/ISSUE_TEMPLATE/preset_submission.yml Explains preset label triage.
extensions/EXTENSION-PUBLISHING-GUIDE.md Corrects the extension validation flow.
presets/PUBLISHING.md Documents the preset workflow trigger.

Review details

Tip

Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

  • Files reviewed: 5/5 changed files
  • Comments generated: 0
  • Review effort level: Balanced

@mnriem
mnriem deleted the mnriem-docs-preset-submission-label branch August 10, 2026 20:50
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