Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
968bb54a
Commit
968bb54a
authored
2 years ago
by
Suzanne Selhorn
Committed by
Amy Qualls
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Removed extra words from titles
Because they were not necessary
parent
a7b11d41
No related branches found
No related tags found
1 merge request
!86088
Removed extra words from titles
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/user/project/repository/push_rules.md
+5
-5
5 additions, 5 deletions
doc/user/project/repository/push_rules.md
with
5 additions
and
5 deletions
doc/user/project/repository/push_rules.md
+
5
−
5
View file @
968bb54a
...
...
@@ -50,7 +50,7 @@ To override global push rules for a specific project:
1.
Set the rule you want.
1.
Select
**Save push rules**
.
##
Use push rules to v
erify users
##
V
erify users
Use these rules to validate users who make commits.
...
...
@@ -59,7 +59,7 @@ Use these rules to validate users who make commits.
-
**Commit author's email**
: Both the author's and committer's email addresses must match the regular expression.
To allow any email address, leave empty.
##
Use push rules to v
alidate commit messages
##
V
alidate commit messages
Use these rules for your commit messages.
...
...
@@ -74,7 +74,7 @@ Use these rules for your commit messages.
the expression. To allow any commit message, leave empty.
Uses multiline mode, which can be disabled by using
`(?-m)`
.
##
Use push rules to v
alidate branches
##
V
alidate branch
nam
es
To validate your branch names, enter a regular expression for
**Branch name**
.
To allow any branch name, leave empty. Your
...
...
@@ -106,7 +106,7 @@ In GitLab 12.10 and later, certain formats of branch names are restricted by
default for security purposes. 40-character hexadecimal names, similar to Git
commit hashes, are prohibited.
##
Use push rules to p
revent unintended consequences
##
P
revent unintended consequences
Use these rules to prevent unintended consequences.
...
...
@@ -116,7 +116,7 @@ Use these rules to prevent unintended consequences.
-
**Do not allow users to remove Git tags with `git push`**
: Users cannot use
`git push`
to remove Git tags.
Users can still delete tags in the UI.
##
Use push rules to v
alidate files
##
V
alidate files
Use these rules to validate files contained in the commit.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment