Skip to content
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

Update pip tools #63632

Merged
merged 4 commits into from Jul 1, 2019
Merged

Update pip tools #63632

merged 4 commits into from Jul 1, 2019

Conversation

mmlb
Copy link
Contributor

@mmlb mmlb commented Jun 21, 2019

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@jonringer
Copy link
Contributor

To adhere to CONTRIBUTING, you will probably want to squash the two commits into one

@mmlb
Copy link
Contributor Author

mmlb commented Jun 30, 2019

Hey @jonringer, that isn't quite the case. CONTRIBUTING.md doesn't state anything on it but does refer to the nixpkgs-manual, and the manual states

Make commits of logical units.

I believe this is what I've done.

@jonringer
Copy link
Contributor

I always took it as atomic "package changes" that all correlated to a given change. This way, all changes can easily be reverted if needed.

@mmlb
Copy link
Contributor Author

mmlb commented Jul 1, 2019

I thought that may be the case too, but then I don't see why not just let the commits be while in the PR state and then "squash and merge"

@zimbatm zimbatm merged commit 52d5b7a into NixOS:master Jul 1, 2019
@mmlb mmlb deleted the update-pip-tools branch July 1, 2019 13:16
@zimbatm
Copy link
Member

zimbatm commented Jul 1, 2019

In that specific case I think it was fine to just push changes until it works and use the squash button at the end. Having separate commits helped me with the review as well.

@mmlb
Copy link
Contributor Author

mmlb commented Jul 1, 2019

yep git rebase -i ftw. A better pr/diff viewer also helps a lot. I'm partial to reviewable.io myself since it doesn't try to take over the development model like gerrit does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants