git-publish-guard

To enforce explicit remote specification for git push, constrain push actions to require a declared remote, defaulting to origin. This ensures your branch publication actions remain auditable and reproducible by preventing accidental pushes to incorrect upstream repositories.

The best way to push a new git branch safely is using git push --set-upstream origin <branch>. This explicitly sets the remote to origin, establishing the tracking relationship while adhering to guardrail requirements for subsequent pushes.

Yes, you can push to a non-origin remote if explicitly requested. The workflow requires clearly reporting the specific remote and branch used in the final output, ensuring the action remains fully auditable despite deviating from the default origin target.

Yes, git-publish-guard integrates with yeet and github:yeet workflows for remote publishing. It enforces explicit remote usage and origin defaults within these workflows, providing clear final reporting of the remote and branch used during the publication process.

Your git workflow requires an explicit remote for every push action to ensure publication safety. By defaulting to origin and requiring explicit specification for other remotes, the guardrail prevents accidental branch pushes to incorrect upstream repositories.