feat: built-in community plugins, profile switches, and working skin center - #12
Merged
Conversation
…center Ship dsh-genui, dsh-annotation, and the dsh-web-ui aggregate inside the Web profile with per-product Settings switches persisted to the profile patch, plus LINUX DO and plugin credits. - Web profile template adds the three community bundles; the web-app bundle declares the aggregate's nine entry packages and the whale-song skin as direct pinned dependencies so the profile module fallback can resolve them - Loopback-only host plugin-control gateway plus the browser Plugin switches tab (restart-time settings) - Desktop declares the plugin-control peer, stages the skin-center skins tree through extraResources, and the postinstall links the workspace copy for source launches - Patch @linxin666/dsh-client-ui-skin-center via patchedDependencies: resolve the skins tree beside an ancestor node_modules, always insert the active skin row (the published aggregate wires none), and reconcile the live Loader tree after apply so packaged Electron, which cannot provide Cordis HMR, applies skins instantly - Bilingual credits for LINUX DO and the three plugin projects; third-party notices regenerated
…ntials Issue lifecycle needs the DSH GitHub App credentials and Issue policy reads its repository identity from the upstream-owned config; both are absent on forks, so the jobs fail on every pull_request event. Guard them to skip cleanly outside the upstream repository.
Job-level if cannot read the secrets context, so the fork guard failed workflow evaluation instead of skipping. Move the credential check onto the token step and gate the handler on the minted token, which lets forks complete the job with all steps skipped.
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
1 participant
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
Ship dsh-genui, dsh-annotation, and the dsh-web-ui aggregate inside the shipped Web profile with per-product Settings switches persisted to the profile patch, plus LINUX DO and plugin credits — and make the packaged desktop app's skin center actually work.
What changed
dsh-host-plugin-controlgateway (list/set-enabled) + a third Settings tab (插件开关) with three product cards writing restart-time{id, disabled}patches to the profile patch.@linxin666/dsh-client-ui-skin-center): resolves theskins/tree beside an ancestornode_modules(bundled deployments have no checkoutpackages/skins), always inserts the active skin's row (the published 0.1.2 aggregate wires none), and reconciles the live Loader tree after apply — packaged Electron cannot provide Cordis HMR, so this is what makes 应用 take effect immediately. Desktop packaging stages the skins tree viaextraResources; a postinstall script links the workspace copy for source launches.Verification
pnpm run buildclean; knip, doc-sync (28 gates), verify-cordis-config, agent-note gates, desktop runtime closure all pass.