-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Document tag_format
and centrally set default value
#775
Document tag_format
and centrally set default value
#775
Conversation
I was very confused about these different usages. Documenting them might be a good basis for future simplification.
This should be non-breaking unless users rely on the looser version validation of TAG_FORMAT_REGEXS compared to their `version_scheme`.
We've been using this default already in `normalize_tag`, but setting this value in the settings dict is cleaner.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #775 +/- ##
==========================================
+ Coverage 97.31% 97.41% +0.10%
==========================================
Files 42 42
Lines 2045 2090 +45
==========================================
+ Hits 1990 2036 +46
+ Misses 55 54 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
Thank @robertschweizer for your contribution! I just read it through, and everything looks good to me!
@woile I'm planning to merge this these days. Let me know if you want to take a deeper look.
Description
Split out from #692.
Please review the commits separately.
Checklist
./scripts/format
and./scripts/test
locally to ensure this change passes linter check and testExpected behavior
Steps to Test This Pull Request
Additional context