Repository navigation
Conversation
…alettes (thetoadsage#7) * Refine dashboard layouts and add provider theme palettes * Add ASCII and Matrix themes with terminal-inspired layouts --------- Co-authored-by: Codex <codex@openai.com>
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
2 participants
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.
The latest main push passed tests and built the container, but publishing was blocked by rejected attribution and an ordinary email address in the squash commit metadata.
This follow-up uses a compliant GitHub noreply identity and adds contributor instructions for validating author/committer metadata, running the release preflight, and reviewing squash messages. The scanner and publishing gate are unchanged. Merging with compliant metadata supplies a clean new push range so verification and publishing can run again.
Validation: the release-safety scan passes against the current main base; release-safety regression tests pass. Application code and data are unchanged.
This restores the next bounded push scan; it does not sanitize existing history or repair the original failed runs. Do not copy rejected attribution into the squash message. A separately authorized history rewrite would be needed to remove historical metadata.