Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Configuring notifications

Choose the type of activity on GitHub Enterprise that you want to receive notifications for and how you want these updates delivered.

En este artículo

¿Te ayudó este documento?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.

Notification delivery options

You have three basic options for notification delivery:

  • the notifications inbox on GitHub Enterprise
  • an email client that uses a verified email address, which can also sync with the notifications inbox on GitHub Enterprise

Tip: Si recibes notificaciones tanto por web como por correo electrónico, puedes sincronizar automáticamente el estado de leído o no leído de las mismas para que las notificaciones web se marquen automaticamente como leídas una vez que las leas en tu correo electrónico correspondiente. Para habilitar esta sincronización, tu cliente de correo electrónico debe poder visualizar imágenes de 'notifications@github.com'.

Benefits of the notifications inbox

The notifications inbox on GitHub Enterprise includes triaging options designed specifically for your GitHub Enterprise notifications flow, including options to:

  • Triage multiple notifications at once.
  • Mark completed notifications as Done and remove them from your inbox. To view all of your notifications marked as Done, use the is:done query.
  • Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the is:saved query.
  • Unsubscribe and remove a notification from your inbox.
  • Preview the issue, pull request, or team discussion where the notification originates on GitHub Enterprise from within the notifications inbox.
  • See one of the latest reasons you're receiving a notification from your inbox with a reasons label.
  • Create custom filters to focus on different notifications when you want.
  • Group notifications in your inbox by repository or date to get a quick overview with less context switching

Benefits of using an email client for notifications

One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months unless you've marked them as Saved. Saved notifications are kept indefinitely. For more information about your inbox's retention policy, see "About notifications."

Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.

Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "Customizing your email notifications."

About participating and watching notifications

When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. To see repositories that you're watching, see https://github.com/watching. For more information, see "Managing subscriptions and notifications on GitHub."

Anytime you comment in a conversation or when someone @mentions your username, you are participating in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking Unsubscribe on the issue or pull request or through the Unsubscribe option in the notifications inbox.

For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on GitHub Enterprise.

Participating and watching notifications options

For example:

  • If you don't want notifications to be sent to your email, unselect email for participating and watching notifications.
  • If you want to receive notifications by email when you've participated in a conversation, then you can select email under "Participating".

If you do not enable watching or participating notifications for web, then your notifications inbox will not have any updates.

Customizing your email notifications

After enabling email notifications, GitHub Enterprise will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on GitHub Enterprise. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.

Únicamente recibirás notificaciones si habilitas el soporte para correo electrónico externo en tu instancia de servidor de GitHub Enterprise. Para obtener más información, contacta a tu administrador de sitio.

Tip: Si recibes notificaciones tanto por web como por correo electrónico, puedes sincronizar automáticamente el estado de leído o no leído de las mismas para que las notificaciones web se marquen automaticamente como leídas una vez que las leas en tu correo electrónico correspondiente. Para habililtar esta sincronización, tu cliente de correo electrónico debe poder visualizar imágenes de las direcciones de tipo no-reply que configuró tu administrador de sitio'.

Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on GitHub Enterprise you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:

  • Comments on issues and pull requests.
  • Pull request reviews.
  • Pull request pushes.
  • Your own updates, such as when you open, comment on, or close an issue or pull request.

Depending on the organization that owns the repository, you can also send notifications to different email addresses for specific repositories. For example, you can send notifications for a specific public repository to a verified personal email address. Your organization may require the email address to be verified for a specific domain. For more information, see “Choosing where your organization’s email notifications are sent."

Solo recibirás correo electrónicos de notificación si optaste por recibir notificaciones por correo electrónico en los ajustes de las notificaciones.

Filtering email notifications

Each email notification that GitHub Enterprise sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all GitHub Enterprise notifications, or certain types of GitHub Enterprise notifications.

If you believe you're receiving notifications that don't belong to you, examine the X-GitHub-Recipient and X-GitHub-Recipient-Address headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.

Email notifications from GitHub Enterprise contain the following header information:

HeaderInformation
From addressThis address will always be 'the no-reply email address configured by your site administrator'.
To fieldThis field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation.
Cc addressGitHub Enterprise will Cc you if you're subscribed to a conversation. The second Cc email address matches the notification reason. The suffix for these notification reasons is en función de la dirección de correo electrónico sin respuesta configurada por el administrador del sitio. The possible notification reasons are:
  • assign: You were assigned to an issue or pull request.
  • author: You created an issue or pull request.
  • comment: You commented on an issue or pull request.
  • manual: There was an update to an issue or pull request you manually subscribed to.
  • mention: You were mentioned on an issue or pull request.
  • push: Someone committed to a pull request you're subscribed to.
  • review_requested: You or a team you're a member of was requested to review a pull request.
  • security_alert: GitHub detected a vulnerability in a repository you receive alerts for.
  • state_change: An issue or pull request you're subscribed to was either closed or opened.
  • subscribed: There was an update in a repository you're watching.
  • team_mention: A team you belong to was mentioned on an issue or pull request.
  • your_activity: You opened, commented on, or closed an issue or pull request.
mailing list fieldThis field identifies the name of the repository and its owner. The format of this address is always <repository name>.<repository owner>.[hostname].
X-GitHub-Severity fieldLas notificaciones de correo electrónico para alertas de seguridad que afecten a uno o más repositorios incluyen el campo de encabezado X-GitHub-Severity. Puedes utilizar el valor del campo de encabezado X-GitHub-Severity para filtrar las notificaciones de correo electrónico para alertas de seguridad. The possible severity levels are:
  • low
  • moderate
  • high
  • critical
For more information, see "About alerts for vulnerable dependencies."

Choosing your notification settings

  1. En la esquina superior derecha de cualquier página, da clic en .
    Notificación que indica cualquier mensaje no leído
  2. En la barra lateral, debajo de la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" para dar clic en Configuración de notificaciones.
    Opciones del menú desplegable "Administrar notificaciones"
  3. On the notifications settings page, choose how you receive notifications when:

Automatic watching

By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.

Automatic watching options

If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.

Choosing where your organization’s email notifications are sent

If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.

Solo recibirás correo electrónicos de notificación si optaste por recibir notificaciones por correo electrónico en los ajustes de las notificaciones.

  1. En la esquina superior derecha de cualquier página, da clic en .
    Notificación que indica cualquier mensaje no leído
  2. En la barra lateral, debajo de la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" para dar clic en Configuración de notificaciones.
    Opciones del menú desplegable "Administrar notificaciones"
  3. Under "Default notification email", select the email address you'd like notifications sent to.
    Default notification email address drop-down
  4. Click Save.

Customizing email routes per organization

If you are a member of more than one organization, you can configure each one to send notifications to any of the email addressed you've added to your GitHub Enterprise account.

  1. En la esquina superior derecha de cualquier página, da clic en .
    Notificación que indica cualquier mensaje no leído
  2. En la barra lateral, debajo de la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" para dar clic en Configuración de notificaciones.
    Opciones del menú desplegable "Administrar notificaciones"
  3. Under "Custom routing," find your organization's name in the list.
    List of organizations and email addresses
  4. Click Edit next to the email address you want to change.
    Editing an organization's email addresses
  5. Select one of your verified email addresses, then click Save.
    Switching your per-org email address

Security alert options

Choose how you want to receive security alerts for repositories that you are watching. You can receive security alerts in your inbox, as a banner on GitHub Enterprise, on the command line, through email, or some combination of these options.

If you want to receive security alerts by email, choose whether you want a weekly email summary of vulnerabilities for up 10 repositories or a new email each time a vulnerability is detected. For more information, see "About alerts for vulnerable dependencies."

Security alerts options

¿Te ayudó este documento?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.