feat: add pinned issue submission hub - #27
Open
joonas-001 wants to merge 1 commit into
Open
joonas-001 wants to merge 1 commit into
joonas-001 wants to merge 1 commit into
Conversation
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.
Summary: records and governs the separately authorized pinned GitHub Issue #26 titled 提交issues请看这里. The pinned hub provides Bug, Feature Request, and Other columns with immediately usable prefilled submission links and existing bug, enhancement, and question labels, plus the private security entry and detailed research link. Governance: general remote synchronization remains disabled; managed labels, milestones, repository/security settings, and test issues remain outside this authorization. Validation: remote GraphQL verification confirmed the rendered three-column table, links, documentation label, and pinned state. Local pnpm release-readiness passed with 147 backend tests and 1 expected skip, 44 frontend tests, 13 static pages, 26 E2E passes and 6 scoped skips, all governance checks, contract drift, and secret scan.