Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D doc
  • Project information
    • Project information
    • Activity
    • Members
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • siteadmin
  • doc
  • Wiki
  • faq

faq · Changes

Page history
commit email hook update authored Feb 06, 2019 by IMBERT Matthieu's avatar IMBERT Matthieu
Hide whitespace changes
Inline Side-by-side
faq.md
View page @ 1aafd945
......@@ -37,7 +37,9 @@ Before leaving Inria:
## How to activate a commit email hook
In your project configuration, section "Integrations/Project services", activate the "Emails on push" service. Then, unfortunately, you need to enter the explicit list of recipients. We haven't found (yet) a way to configure this such that the list of project members is automatically used as the recipients list
Gitlab's model is that instead of setting up a centralized commit email hook per project, it is rather up to the users to choose his/her notification level per project. All users can set their 'global' notification level setting in their account settings. Then they can override this default global notification level per project on top of the project details page, with the little bell (This way, a project cannot impose a notification level to its members).
If you still want something similar to the old commit email hooks, then in your project configuration, section "Integrations/Project services", activate the "Emails on push" service. Then, unfortunately, you need to enter the explicit list of recipients. We haven't found a way to configure this such that the list of project members is automatically used as the recipients list
## How to rewrite history
......
Clone repository
  • Forge to Gitlab migration FAQ
  • faq
  • Home