-
Georges Racinet authored
Post-receive notificiations are necessary to trigger pipelines and other post branch update actions that must be taken on the GitLab side Previously, we enabled them in merges with changeset performed by the Rails app itself, but we had only the publication step send them to avoid unnecessary consequences like redundant pipelines, but that was wrong: if there's already an added commit on `branch/default` a publication doesn't trigger any change on `branch/default`. The only post-receive it can send is a topic branch prune.
376d59c06826Georges Racinet authoredPost-receive notificiations are necessary to trigger pipelines and other post branch update actions that must be taken on the GitLab side Previously, we enabled them in merges with changeset performed by the Rails app itself, but we had only the publication step send them to avoid unnecessary consequences like redundant pipelines, but that was wrong: if there's already an added commit on `branch/default` a publication doesn't trigger any change on `branch/default`. The only post-receive it can send is a topic branch prune.
Loading