Repository navigation
feat(community): add contributor entry points and handoffs - #36
Merged
Merged
Conversation
This was referenced Oct 22, 2026
Closed
- 以实现项目表达 scope，以发布元数据表达交付范围 - 补全选题、包权限与 fork CI 的贡献前提
xiaoland
force-pushed
the
feat/ecosystem-contribution-dx
branch
from
October 25, 2026 06:27
ae57618 to
5a2cf1e
Compare
This was referenced Oct 26, 2026
Closed
- Route questions, task proposals, and security reports to the right entry points - Define task readiness, next responders, and cross-repository delivery tracking - Link the public community and current work board from the organization profile
xiaoland
added
documentation
xiaoland
changed the title
- Use Bug and Task in issue forms instead of type labels. - Keep coordination status and priority in the mixed project board. - Limit labels to discovery, automation, and preserved historical context.
xiaoland
marked this pull request as ready for review
October 26, 2026 07:02
github-project-automation
Bot
moved this from Review / acceptance
to Done
in InKCre Current Work
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
External contributors need a question entry point, actionable issues, and a visible next responder on PRs. This adds default forms using native Bug/Task issue types, SUPPORT and profile links, and triage and handoff guidance. Project Status/Priority handle coordination for issues and PRs; labels identify contribution opportunities and actual automation needs. It also distinguishes implementation scopes from release selection.
Primary scope:
community. Affected release projects: none.Tracking issue: #39.
Evidence
Next action
Merged after explicit maintainer authorization. The live issue chooser was verified in impl-swift and impl-ts, including the latter's existing local PR template. The inherited Bug and Task forms render their required fields and set the intended native Type without applying type labels. Q&A, Ideas, private reporting, blank issues, and the inherited contribution/support links are available. No test issue was submitted.
Risk and rollback
Repositories without local templates inherit these defaults. Existing branch protection, approval counts, and fork credential boundaries are unchanged. Revert this PR to restore the previous files. Live discussions, issue comments, labels, and project metadata have their own history and are not deleted by a code revert.
Delivery effects
No package publication, migration, or credential change. Community files are active on main and inherited-form acceptance passed.
Related work
No stacked parent or child PR.