Skip to content

0.4.2 — git commit -F is not a force push

Choose a tag to compare

View all tags
@BGMLAI BGMLAI released this 08 Jul 12:16
v0.4.2
9a55712

False-positive fix, shipped the same day it was found (while dogfooding the 0.4.1 release — see #4 and discussion #5).

  • GIT_FORCE_PUSH no longer false-blocks git commit -F file followed by a push. The short force flag is now matched case-sensitively, so -F (message-from-file) is no longer read as the force flag. Verified in a clean venv against this PyPI release, all four directions: -F allows · short force flag blocks · long force flag blocks · --force-with-lease allows.
  • CI green: 892 passed / 28 skipped / 0 failed on py3.11–3.13 (run); regression case added to the bypass suite's benign set.
  • PyPI long description now carries the demo GIFs and the "Verify the numbers" section (they landed in the README after 0.4.1 was frozen — closes #3).

PyPI: https://pypi.org/project/gate.cat/0.4.2/ · Still open from the same dogfood batch: the multiline commit-message inert-literal gap (#4).

Assets 2
Loading