Fix firing ref update event for change creation
Because of Ic888248f1fec27a5f9d84afc85ac035eecfa6607 which removed the duplicate ref updates for refs/changes/*. The ref update event will not be fired in ChangeInserter anymore. Add the ref update event back when BatchRefUpdate process commands. Change-Id: Ie9a132e107def33bdd513b7854b50de911edba0d
This commit is contained in:
@@ -652,12 +652,8 @@ public class ReceiveCommits {
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
if (!MagicBranch.isMagicBranch(refName)
|
if (!MagicBranch.isMagicBranch(refName)) {
|
||||||
&& !refName.startsWith(REFS_CHANGES)) {
|
|
||||||
logDebug("Firing ref update for {}", c.getRefName());
|
logDebug("Firing ref update for {}", c.getRefName());
|
||||||
// We only fire gitRefUpdated for direct refs updates.
|
|
||||||
// Events for change refs are fired when they are created.
|
|
||||||
//
|
|
||||||
gitRefUpdated.fire(project.getNameKey(), c, user.getAccount());
|
gitRefUpdated.fire(project.getNameKey(), c, user.getAccount());
|
||||||
} else {
|
} else {
|
||||||
logDebug("Assuming ref update event for {} has fired",
|
logDebug("Assuming ref update event for {} has fired",
|
||||||
|
|||||||
Reference in New Issue
Block a user