-
Bug
-
Resolution: Fixed
-
High
-
5.0.0
-
None
-
Severity 2 - Major
-
Repository hooks that use PreRepositoryHook and/or PostRepositoryHook which were introduced in 5.0 that register a RepositoryHookCommitCallback can incorrectly get a onCommitAdded callback for commits that were neither added or removed, but are instead ancestors of the updated branch.
More specifically, this happens when for branches that are updated by merging in another branch.
[BSERV-9802] RepositoryHookCommitCallback sometimes incorrectly returns commits that have not been added or removed to ref
| Workflow | Original: Stash Workflow - Restricted [ 2021626 ] | New: JAC Bug Workflow v3 [ 3133815 ] |
| Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: To be reviewed [ 10026 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 5.0.2 [ 72009 ] |
| Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | New: Michael Heemskerk [ mheemskerk ] |
| Description |
Original:
Repository hooks that use {{PreRepositoryHook}} and/or {{PostRepositoryHook}} which were introduced in 5.0 that register a {{RepositoryHookCommitCallback}} can incorrectly get a {{onCommitAdded}} callback for commits that were neither added or removed, but are instead common ancestors of the updated branch.
More specifically, this happens when for branches that are updated by merging in another branch. |
New:
Repository hooks that use {{PreRepositoryHook}} and/or {{PostRepositoryHook}} which were introduced in 5.0 that register a {{RepositoryHookCommitCallback}} can incorrectly get a {{onCommitAdded}} callback for commits that were neither added or removed, but are instead ancestors of the updated branch.
More specifically, this happens when for branches that are updated by merging in another branch. |
| Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |
| Description |
New:
Repository hooks that use {{PreRepositoryHook}} and/or {{PostRepositoryHook}} which were introduced in 5.0 that register a {{RepositoryHookCommitCallback}} can incorrectly get a {{onCommitAdded}} callback for commits that were neither added or removed, but are instead common ancestors of the updated branch.
More specifically, this happens when for branches that are updated by merging in another branch. |