Commit e87728dc authored by Sean McGivern's avatar Sean McGivern

Merge branch 'fix-wording-on-push-rules' into 'master'

Remove superfluous wording on push rules

See merge request !1811
parents 138046ff 9ba00a10
......@@ -2,7 +2,7 @@
%h3.page-title
Pre-defined push rules.
%p.light
Rules that define what git pushes are accepted for a project. All newly created projects will use this settings. Request new rules for free by creating an issue on the <a href="https://gitlab.com/gitlab-org/gitlab-ee/issues/">GitLab EE issue tracker</a> and labeling it 'Feature proposal'. Or if you can please contribute a tested merge request.
Rules that define what git pushes are accepted for a project. All newly created projects will use this settings.
%hr.clearfix
......
.row.prepend-top-default.append-bottom-default
.col-lg-3
%h4.prepend-top-0
Push Rules
%p.light
Push Rules outline what is accepted for this project. You can request new rules (for free) by creating an issue on our
= succeed '.' do
%a{ href: "https://gitlab.com/gitlab-org/gitlab-ee/issues/" }GitLab EE issue tracker
Alternatively, submit a merge request to GitLab EE.
Push Rules outline what is accepted for this project.
.col-lg-9
%h5.prepend-top-0
Add new push rule
......
---
title: 'Remove superfluous wording on push rules'
merge_request: 1811
......@@ -8,10 +8,6 @@ GitLab Enterprise Edition offers a user-friendly interface for such cases.
Push Rules are defined per project so you can have different rules applied to different projects depends on your needs.
Push Rules settings can be found at Project settings -> Push Rules page.
## New hooks
If you are a subscriber and need a hook that is not there yet we would be glad to add it for free, please contact support to request one.
## How to use
Let's assume you have the following requirements for your workflow:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment