Closed anotherbridge closed 2 months ago
not sure if it's a good idea to apply make fix
here, as obviously change is not really atomic anymore - what do you think @sosthene-nitrokey or @robin-nitrokey ?
I think it’s fine. The commits are atomic, and atomic PRs is something that is neither achievable nor even desirable.
Though I wonder why these changes occur in the first place – some linting dependency that we didn’t pin hard enough? New Python version?
I think we should manually cherry-pick a0ce77970ad9ecf0f3e0e02a7133724eef977195 instead of merging.
I’m really confused now. Why can’t we start a CI run for this PR? And why did make fix
perform these changes in the first place? When testing locally, make check
fails with these changes, so we should not merge them.
weird, I would also expect that the CI should run this.... https://github.com/Nitrokey/pynitrokey/blob/600527eac2acb25e811a8e1bbedf8d4a09431b28/.github/workflows/ci.yaml#L6
but, ok let's only include the first commit, @anotherbridge can you be so kind and remove the make fix
commit, just include https://github.com/Nitrokey/pynitrokey/pull/509/commits/a0ce77970ad9ecf0f3e0e02a7133724eef977195 in this PR please - think something went wrong with your python version maybe ?
For first-time contributors, CI runs need to be approved. I did that recently, but I don’t remember if it was for this PR. Anyway, either the CI run should show up, or the option to approve and trigger it.
@daringer @robin-nitrokey @sosthene-nitrokey I removed the commit that includes the make fix
and also merged your master branch into my fork.
Rebased and merged. Thank you!
Added a short version to call the help, i.e. now the help of a functionality is available by calling
--help
and-h
.Changes
nitropy
command.Checklist
make check
make fix
Test Environment and Execution
v1.6.0-test.20231218