Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
ee815e6c
Commit
ee815e6c
authored
4 years ago
by
Manoj M J
Committed by
Albert Salim
4 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix wording in Danger when warning about number of lines changed
parent
d82ba779
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
danger/changes_size/Dangerfile
danger/changes_size/Dangerfile
+2
-2
No files found.
danger/changes_size/Dangerfile
View file @
ee815e6c
...
@@ -13,7 +13,7 @@
...
@@ -13,7 +13,7 @@
# end
# end
if
git
.
lines_of_code
>
2_000
if
git
.
lines_of_code
>
2_000
warn
"This merge request is definitely too big (
more than
#{
git
.
lines_of_code
}
lines changed), please split it into multiple merge requests."
warn
"This merge request is definitely too big (
#{
git
.
lines_of_code
}
lines changed), please split it into multiple merge requests."
elsif
git
.
lines_of_code
>
500
elsif
git
.
lines_of_code
>
500
warn
"This merge request is quite big (
more than
#{
git
.
lines_of_code
}
lines changed), please consider splitting it into multiple merge requests."
warn
"This merge request is quite big (
#{
git
.
lines_of_code
}
lines changed), please consider splitting it into multiple merge requests."
end
end
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment