Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

repository_push.rb

Forked from GitLab.org / GitLab FOSS
Source project has a limited visibility.
  • Sean McGivern's avatar
    5f27e26b
    Only generate repository push email once · 5f27e26b
    Sean McGivern authored
    The repository push email can be very expensive to generate, especially
    with syntax-highlighted diffs. Instead of generating the email for each
    recipient, generate one email object and reset the Message-Id and To
    headers for each recipient. (Cloning would also be expensive in the case
    of large emails, although probably not as bad as generating from
    scratch.)
    5f27e26b
    History
    Only generate repository push email once
    Sean McGivern authored
    The repository push email can be very expensive to generate, especially
    with syntax-highlighted diffs. Instead of generating the email for each
    recipient, generate one email object and reset the Message-Id and To
    headers for each recipient. (Cloning would also be expensive in the case
    of large emails, although probably not as bad as generating from
    scratch.)