Establish Faceplate repository baseline - #1
Merged
Merged
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
Establishes Faceplate as a neutral, appliance-focused downstream of kmscon while preserving the upstream history.
mainandrelease/*branch rulesetsBranding decision
The core remains vendor-neutral. A Dataplicity-branded build must consume separately licensed runtime theme assets at image-build time; the logo must not be compiled into Faceplate.
Validation
mainmatches upstream commit791e659f2420e00cda7c39b4eb53f3c2844b4885git diff --checkmeson format --recursive --check-onlyFollow-up after merge
Apply the documented GitHub rulesets to
mainandrelease/*, require the named CI checks plus GitHub's default CodeQL check, enable automatic branch updates, and use squash merges.