Fix fatal in Git hook when a --force push completely rewrites a ref
ClosedPublic
Actions

Authored by epriestley on Dec 11 2013, 8:31 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Thu, Jun 26, 7:36 PM

	Unknown Object (File)
	May 10 2025, 6:31 AM

	Unknown Object (File)
	Apr 26 2025, 7:37 AM

	Unknown Object (File)
	Apr 24 2025, 10:57 AM

	Unknown Object (File)
	Apr 24 2025, 10:57 AM

	Unknown Object (File)
	Apr 24 2025, 10:57 AM

	Unknown Object (File)
	Apr 24 2025, 8:43 AM

	Unknown Object (File)
	Apr 23 2025, 7:06 PM

View All Files

Subscribers

aran

Details

Reviewers

btrahan

Maniphest Tasks

T4224: Failure when trying to force push

Commits

Restricted Diffusion Commit
rP61c934449d17: Fix fatal in Git hook when a --force push completely rewrites a ref

Summary

Fixes T4224. If you git merge-base A B, and they have no ancestor, the command exits with an error. Assume errors mean "no ancestry" and continue.

Test Plan

Completely rewrite a repository with a --force push.

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

btrahan accepted this revision.Dec 11 2013, 10:33 PM

Closed by commit rP61c934449d17 (authored by @epriestley).

Revision Contents
Changeset List

Path

Size

src/

applications/

diffusion/

engine/

DiffusionCommitHookEngine.php

15 lines

Diff 17546

View Options

src/applications/diffusion/engine/DiffusionCommitHookEngine.php

Fix fatal in Git hook when a --force push completely rewrites a refClosedPublicActions