feat(repo): client-side git guardrails (Husky.NET pre-push hook)#18
Merged
Conversation
Portable pre-push guard replicated from Chrison-dev/Homelab: blocks direct pushes to the trunk, force/non-fast-forward pushes, and pushes onto a branch whose PR is already MERGED/CLOSED. Bypass: git push --no-verify. Activate per clone: dotnet tool restore && dotnet husky install Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added a commit
that referenced
this pull request
Jul 23, 2026
* build: Fallout CI + nuget.org Trusted Publishing (Chrison.* IDs) Convert the build/CI to the Fallout pipeline and retarget publishing from GitHub Packages to nuget.org via Trusted Publishing (OIDC, no stored key). - build/: Fallout build project (Compile/Test/Pack/Publish targets) + build.sh/ps1 + .fallout/ root marker; nuget.config gains the Fallout-build feed (Fallout.* only). - Rename package IDs to the Chrison.* prefix (Chrison.ProxmoxSharp[.Api|.Cli]) — the bare ProxmoxSharp/UnifiSharp IDs are taken on nuget.org by unrelated projects. AssemblyName/RootNamespace stay ProxmoxSharp, so `using ProxmoxSharp;` is unchanged. - ci.yml → build+test only; publish.yml → NuGet/login@v1 OIDC → dotnet push to nuget.org (prerelease on main, stable on v* tag). - Fix CI regression: restore microsoft.openapi.kiota 1.31.1 to the tool manifest (dropped in #18), which broke the codegen step — CI red since 2026-06-29. - README: Build/CLI/Packages sections updated for Fallout + Chrison.* on nuget.org. Verified locally: ./build.sh Pack → 40 tests pass, emits Chrison.ProxmoxSharp*.nupkg. Requires (repo/org setup): PACKAGES_PAT secret (read:packages on Fallout-build), NUGET_USER secret (nuget.org profile), and a nuget.org Trusted Publishing policy for this repo + publish.yml. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(publish): run in the Nuget.org environment for Trusted Publishing The nuget.org TP policy scopes to Environment=Nuget.org, so the publish job must declare `environment: Nuget.org` — the OIDC token only carries the environment claim when the job sets it, and the token exchange is rejected otherwise. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
Replicates the pre-push guard from Chrison-dev/Homelab (PR #211). Blocks direct trunk pushes, force/non-ff pushes, and pushes onto an already-merged/closed branch. Bypass:
git push --no-verify. Activate per clone:dotnet tool restore && dotnet husky install.🤖 Generated with Claude Code