1.5 KiB
| stage | group | info | gitlab_dedicated | description | title |
|---|---|---|---|---|---|
| Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | yes | Configure limits on the number of single push events your instance will allow. | Push event activities limit and bulk push events |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
To maintain good system performance and prevent spam on the activity feed, set a Push event activities limit.
By default, GitLab sets this limit to 3. When you push changes that affect more than 3 branches and tags,
GitLab creates a bulk push event instead of individual push events.
For example, if you push to four branches simultaneously, the activity feed displays a single
{{< icon name="commit">}} Pushed to 4 branches at (project name) event instead of four separate
push events.
To set a different Push event activities limit, either:
-
In the Application settings API, set the
push_event_activities_limit. -
In the GitLab UI:
- On the left sidebar, at the bottom, select Admin.
- On the left sidebar, select Settings > Network.
- Expand Performance optimization.
- Edit the Push event activities limit setting.
- Select Save changes.
The value can be greater than or equal to 0. Setting this value to 0 does not disable throttling.