feat: aliases-git v1.24.0 - add -NoVerify switch to push aliases - #272
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR extends the aliases-git PowerShell module by adding a -NoVerify switch to push-related alias functions so callers can append git push --no-verify to skip pre-push hooks, and bumps the module version accordingly. It also refreshes a couple of Python lockfile dependencies.
Changes:
- Add
-NoVerifyto core push aliases and commit+push combo aliases, forwarding the switch only to push invocations. - Extend
-NoVerifysupport to helper-module push paths (merge/rebase flows and remote branch deletion helpers). - Bump
aliases-gitModuleVersion to1.24.0and refreshuv.lock(certifi, platformdirs).
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| uv.lock | Refresh locked dependency versions (certifi, platformdirs). |
| modules/aliases-git/Functions/helper.ps1 | Add -NoVerify handling to helper push/delete flows. |
| modules/aliases-git/Functions/alias.ps1 | Add -NoVerify to push aliases and commit+push combos (forwarded to push only). |
| modules/aliases-git/aliases-git.psd1 | Bump module version to 1.24.0. |
Comments suppressed due to low confidence (1)
modules/aliases-git/Functions/helper.ps1:107
--no-verifyis being appended after the branch/refspec (e.g.git push --delete <remote> <branch> --no-verify). Ingit push, options must come before the remote/refspecs; placing--no-verifyafter the branch is likely parsed as another refspec and can fail.
$commands.Add("git push --delete $remote $Branch$($NoVerify ? ' --no-verify' : '')")
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
szymonos
force-pushed
the
aliases-git-1232
branch
from
July 23, 2026 05:26
295e88b to
07ce932
Compare
szymonos
force-pushed
the
aliases-git-1232
branch
from
July 23, 2026 05:34
07ce932 to
6be5e39
Compare
szymonos
force-pushed
the
aliases-git-1232
branch
from
July 23, 2026 05:48
6be5e39 to
e6f5cfd
Compare
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
-NoVerifyswitch to everyaliases-gitfunction that runsgit pushorgit commit, appending--no-verifyto skip the corresponding hooks (pre-push / pre-commit). Chosen over name-encoded variants (gpushnv,gcmsgnvp, ...) to avoid a combinatorial explosion of alias names - one orthogonal switch instead.gcam -NoVerifyskips the commit hook;gcamp -NoVerifyskips the push hook;gcamp 'msg' --no-verify -NoVerifydoes both (raw--no-verifyflows to the commit, switch to the push).Invoke-WriteExecCommandgained the-NoVerifyswitch and appends--no-verifyafter all arguments - the correct position for bothgit pushandgit commit -m 'msg'(must follow the message). Single-command aliases just declare the switch and splat; no per-function string-building.gpushoat,gmgo,grbo,gbdo,gbdo!) keep embedding--no-verifyon the specific push, since a blanket append would wrongly hit a siblingfetch/merge/branch --delete.-NoVerifyto the right sub-command (inner commit vs. push).aliases-gitModuleVersion1.23.1 -> 1.24.0 (MINOR: new backward-compatible capability).chore: bump dependencies- routineuv.lockrefresh (certifi, platformdirs).Test plan
make lint-diff- all pre-commit hooks green[Parser]::ParseFile) and imports without error-WhatIfsmoke tests across all categories confirm correct--no-verifyplacement:gcmsg 'msg' -NoVerify->git commit -m 'msg' --no-verify(after the message)gpush -NoVerify->git push --no-verifygcamp 'msg' -NoVerify-> commit clean,git push --no-verify(last-in-chain)gcamp 'msg' --no-verify -NoVerify-> both commit and push get--no-verifygpushoat -NoVerify->--no-verifyon both push legs of the&&🤖 Generated with Claude Code