-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
FEAT: Add configuration files #55
Conversation
5e09c6a
to
ba63ef8
Compare
Okay, this could count as an MVP. Unfortunately, I'm not sure I have the bandwidth to write some tests right now. |
Thanks, I'll try to review it soon. I'll see if I can also add some tests 👍 |
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.
Thanks a lot! Some things to change. If you don't have the capacity right now, I'll handle it when I get some time, no worries 👍
41964c2
to
5af203f
Compare
This commit addresses [this comment (pawamoy#55)](pawamoy#55 (comment)). Please note that this will disallow unsetting options if a hierarchy of config files were to be implemented at some point.
This commit addresses [this comment (pawamoy#55)](pawamoy#55 (comment)). Please note that this will disallow unsetting options if a hierarchy of config files were to be implemented at some point.
5b3ee64
to
89ce6dc
Compare
…sion to bump to, as well as `auto`, `major`, `minor` or `patch` Issue pawamoy#38: pawamoy#38 PR pawamoy#41: pawamoy#41 Co-authored-by: Timothée Mazzucotelli <pawamoy@pm.me>
This commit addresses [this comment (pawamoy#55)](pawamoy#55 (comment)). Please note that this will disallow unsetting options if a hierarchy of config files were to be implemented at some point.
89ce6dc
to
89a1af3
Compare
Okay, I think this is getting there. However, I've hit some stomper with I believe this test is actually just checking that the input is parsed and default settings are set, so I would just remove it (I don't think it covers anymore lines than the other tests). The problem with the test is that it is checking two different things - whether the settings are properly parsed and then the call to main. If the goal is to see that the parser is working, I suggest just testing LMKWYT |
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.
Thanks for following through, and for implementing things with care 🙂
LGTM, just a few suggestion (minor changes).
I'll take a look. |
Actually the test failures I see in CI are weird. If you look at the second and third last runs, there are 2 or 3 tests failing, all because of the |
OK, better. However we're hitting this: I think there's a race condition in the tests. We shouldn't create test files in the repository folder, but rather use a tmp directory, move there and only then test things. EDIT: oh but you're already doing that. Not sure what's happening. Will continue to investigate. EDIT 2: oh of course, |
I've fixed the tests, applied Black formatting, and finished fixing Mypy warnings. I'm ready to squash and merge, let me know if there's anything else you'd like to do before that. And thanks again for your amazing work 🚀 |
All good on my end. Thanks for the tool and for taking this PR over the
finish line.
…On Mon, Aug 21, 2023, 23:56 Timothée Mazzucotelli ***@***.***> wrote:
I've fixed the tests, applied Black formatting, and finished fixing Mypy
warnings. I'm ready to squash and merge, let me know if there's anything
else you'd like to do before that. And thanks again for your amazing work 🚀
—
Reply to this email directly, view it on GitHub
<#55 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAESDRQH4DODUD376JTQSU3XWPKSVANCNFSM6AAAAAA3VIU3MI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Good catch on the regular expressions written in TOML! |
Permit git-changelog be configured permanently via config files.
Resolves: #54.