-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DescriptionCheck: catch ending with a full stop #472
base: master
Are you sure you want to change the base?
Conversation
Bug: https://bugs.gentoo.org/729968 Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
Codecov ReportBase: 81.09% // Head: 81.09% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #472 +/- ##
========================================
Coverage 81.09% 81.09%
========================================
Files 55 55
Lines 7923 7925 +2
Branches 1474 1775 +301
========================================
+ Hits 6425 6427 +2
Misses 1400 1400
Partials 98 98
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
s = desc.lower() | ||
if s.startswith("based on") and "eclass" in s: | ||
yield BadDescription("generic eclass defined description", pkg_desc=desc, pkg=pkg) | ||
elif s in (pkg.package.lower(), pkg.key.lower()): | ||
yield BadDescription("generic package description", pkg_desc=desc, pkg=pkg) | ||
elif desc.endswith(tuple(".,:;")): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Err but it's fine if it's a proper sentence? Unless we don't want sentence-type descriptions, then we should say that explicitly. But I don't think we want to do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we're clear on this. I always took the rule to be that we don't want to terminate in a full-stop. I suppose if there's a previous full stop before the end, we might want another?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could I get explanation of that new rule? I'm unable to understand it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Long time ago this was considered for repoman... and, if I don't misremember, it was finally reverted because of people thinking differently on this :/
https://bugs.gentoo.org/438976
Bug: https://bugs.gentoo.org/729968
results on gentoo tree