When delegated bypass for push protection is enabled, designated reviewers can approve or deny requests from contributors who want to push commits containing secrets.
This article explains how to review and manage bypass requests for repositories and organizations.
For more information about how bypass requests work, see Обход запросов для защиты от пуша.
Managing requests for a repository
-
На GitHubперейдите на главную страницу репозитория.
-
Под названием репозитория нажмите на Security вкладку. Если вы не видите вкладку « Security» — выберите выпадающее меню и нажмите Security.
-
В левой боковой панели в разделе "Запросы" щелкните "Отправить обход защиты".
-
Select the All statuses dropdown menu, then click Open to view requests that are awaiting review, and those that have been approved but for which the commits haven't been pushed to the repository yet.
-
Click the request that you want to review.
-
Review the details of the request.
-
При необходимости добавьте комментарий проверки. Комментарий будет добавлен на временную шкалу запроса проверки и временную шкалу оповещений secret scanning. Например, вы можете объяснить причину утверждения или отказа в запросе на аудит и отчеты, а также предложить дальнейшие шаги для участника.
-
To allow the contributor to push the commit containing the secret, click Approve bypass request. Or, to require the contributor to remove the secret from the commit, click Deny bypass request.
Managing requests for an organization
Organization owners, security managers and organization members with the relevant fine-grained permission (via a custom role) can review and manage bypass requests for all repositories in the organization using security overview. See Проверка запросов на обход защиты push-уведомлений.
Filtering requests
You can filter requests by:
- Approver (member of the bypass list)
- Requester (contributor making the request)
- Timeframe
- Status
Filtering by status
The following statuses are assigned to a request:
| Status | Description |
|---|---|
Cancelled | The request has been canceled by the contributor. |
Completed | The request has been approved and the commit(s) have been pushed to the repository. |
Denied | The request has been reviewed and denied. |
Expired | The request has expired. Requests are valid for 7 days. |
Open | The request has either not yet been reviewed, or has been approved but the commit(s) have not been pushed to the repository. |