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

gyp: update gyp to v0.9.1 #2402

Merged
merged 1 commit into from May 27, 2021
Merged

Conversation

gengjiawen
Copy link
Member

Features

  • use LDFLAGS_host for host toolset (#98) (bea5c7b)

Bug Fixes

  • msvs.py: remove overindentation (#102) (3f83e99)
  • update gyp.el to change case to cl-case (#93) (13d5b66)

@gengjiawen gengjiawen requested a review from cclauss May 19, 2021 07:45
@@ -1,7 +1,7 @@
on:
push:
branches:
- master
- main
Copy link
Contributor

@cclauss cclauss May 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not a fan of master --> main but it is all the rage these daze...

  1. We need to document how contributors change their local forks.
  2. We need to document how contributors change the 29 open PRs.
  3. https://github.com/nodejs/node-gyp/blob/master/.github/workflows/release-please.yml#L6 must change.
  4. We need to document how this change effects the repo chain of gyp-next --> node-gyp --> node.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's in https://github.com/nodejs/gyp-next. The change to main branch has been made in nodejs/gyp-next#103 by @targos . It's out of scope for this repo :)

Copy link
Contributor

@DeeDeeG DeeDeeG May 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's out of scope for this repo :)

👍

If that topic does come up here, or elsewhere in the Node ecosystem, most of the documentation around that from GitHub is collected here: https://github.com/github/renaming/

(Using the GitHub.com UI to rename a branch from master to main will cause GitHub to seamlessly handle most of it behind the scenes, according to the bullet points at the bottom of that repo's README.md.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Every contributor needs to do this for 1. How do they do 2.?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. is done automatically by github when the branch is renamed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Copy link
Contributor

@cclauss cclauss May 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The destination branches of all 29 pull requests are changed automatically?!?

Like commit into nodejs:master at the top of this page:

gengjiawen wants to merge 1 commit into nodejs:master from gengjiawen:feat/gyp_bump

Cool! Thanks.

Copy link
Contributor

@DeeDeeG DeeDeeG May 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is easier to understand the instructions for 1. with long flags rather than short flags... (And I added links to the git subcommand documentation)

$ git branch --move OLD-BRANCH-NAME NEW-BRANCH-NAME
$ git fetch origin
$ git branch --set-upstream-to=origin/NEW-BRANCH-NAME NEW-BRANCH-NAME
$ git remote set-head origin --auto


### Bug Fixes

* py lint ([3b6a8ee](https://www.github.com/nodejs/gyp-next/commit/3b6a8ee7a66193a8a6867eba9e1d2b70bdf04402))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://www.pylint.org is not something that we use (because we use flake8 instead) so this comment might confuse some readers but we should push forward with this release.

Copy link
Contributor

@cclauss cclauss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gengjiawen gengjiawen merged commit 4d03652 into nodejs:master May 27, 2021
@gengjiawen gengjiawen deleted the feat/gyp_bump branch May 27, 2021 14:05
gengjiawen added a commit that referenced this pull request May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants