Repository navigation
Optimize preview command and improve commit message handling - #22
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.
This pull request significantly expands and clarifies the documentation for
pubgate, focusing on the newpreviewcommand, improved auxiliary directory handling, stricter public publishing requirements, and more detailed CLI and configuration references. The updates make the workflows, options, and edge cases much clearer, and introduce new features for local testing and auxiliary content management.Major documentation improvements and new features:
New Features and Workflow Enhancements
previewcommand that allows users to generate a local-only filtered worktree from any clean local commit for testing, without requiring a merge tomainor interaction with the public repo. This is now documented in both the workflow and CLI reference sections. [1] [2] [3] [4]CLI Reference and Option Clarifications
publishworkflow (explicit author name/email/message). [1] [2]Edge Cases and Error Handling
preview, auxiliary directory management, and Git LFS handling, including how preview interacts with LFS and what happens if auxiliary sources are missing. [1] [2]Security and Public Release Process
publishnow requires a public author identity and commit message, never leaking internal metadata or using internal signing keys. [1] [2] [3]Internal Consistency and Spec Updates
These changes provide much clearer guidance for both new and existing users, and introduce important new capabilities for local testing and auxiliary data management.