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

nodePackages: netlify-cli init at 2.59.1 #80770

Merged
merged 1 commit into from Aug 27, 2020

Conversation

matthuszagh
Copy link
Contributor

@matthuszagh matthuszagh commented Feb 22, 2020

Motivation for this change

Adds the netlify-cli tool. Used generate.sh to create the nix build expressions, so this also updates other packages.

Things done

Added netlify-cli to node-packages-v10.json and then ran ./generate.sh.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-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)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@matthuszagh matthuszagh changed the title nodePackages: netlify-cli init at 2.35.0 nodePackages: netlify-cli init at 2.40.0 Apr 6, 2020
@matthuszagh
Copy link
Contributor Author

I've updated this to fix merge conflicts.

@utdemir
Copy link
Member

utdemir commented May 13, 2020

I tested this on NixOS and deployed a website with it without any problems.

I think it might also make sense to add an entry to the top-level package set too.

@prusnak
Copy link
Member

prusnak commented May 30, 2020

Please rework your PR. It now has a merge conflict after PR #89184 has been merged

@matthuszagh
Copy link
Contributor Author

@prusnak I've updated this to use the new scheme. Added it to node-packages.json and used generate.sh. It builds on nodePackages and nodePackages_latest.

@utdemir in regard to adding a top-level package, this is the only node package I've contributed, so I'll defer to someone who's more familiar with nixpkgs and node packages.

@utdemir
Copy link
Member

utdemir commented Jun 16, 2020

I do not know who to ping, but it'd be good to have this package in nixpkgs. It looks like it gets a merge conflict on node-package.nix while waiting for a merge; so maybe someone with a commit right should do the rebase too.

@matthuszagh
Copy link
Contributor Author

@calbrecht I'm not sure if you're the right person to ping for a review here. Please excuse me if not. If you would be willing to provide a review, let me know and I'll fix the merge conflicts before you review (node-packages.nix is changed frequently so it doesn't make sense for me to try to keep this up-to-date before it's reviewed). Thanks!

@matthuszagh
Copy link
Contributor Author

I've gone ahead and resolved the conflicts.

@calbrecht
Copy link
Member

@matthuszagh, lgtm 👌 Thanks.
Have no merge rights, too :)

@matthuszagh
Copy link
Contributor Author

@globin, would you be willing to review this PR? If so, let me know and I'll resolve the merge conflicts. Thanks!

@mrkkrp
Copy link
Member

mrkkrp commented Aug 15, 2020

It would be nice to merge this.

@matthuszagh
Copy link
Contributor Author

@mrkkrp agreed. Unfortunately, I'm not sure who the right person to contact for that is. If you do know, mind notifying them? When someone with merge rights agrees to review this, I'll go ahead and resolve the merge conflicts.

@matthuszagh
Copy link
Contributor Author

@infinisil would you be willing to review this PR? I noticed you merged pyright, but if you're not the right person for this would you happen to know who is? If you are willing, let me know and I'll fix the merge conflicts first. Thanks!

@infinisil
Copy link
Member

Looks good to me, I can merge it if you re-update the node packages. Feel free to ping me when done :)

@matthuszagh
Copy link
Contributor Author

Thanks so much @infinisil! I've fixed the merge conflicts. One remaining question: should I add a top-level package for this, or just leave it as is?

@matthuszagh matthuszagh changed the title nodePackages: netlify-cli init at 2.40.0 nodePackages: netlify-cli init at 2.59.1 Aug 27, 2020
@infinisil
Copy link
Member

Since this is not really a node package but only happens to be written with node, it would make sense to add a top-level package.

@matthuszagh
Copy link
Contributor Author

@infinisil done.

@infinisil infinisil merged commit f956759 into NixOS:master Aug 27, 2020
@matthuszagh matthuszagh deleted the netlify-cli branch August 27, 2020 03:12
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

6 participants