Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@JMGordon
Copy link

@JMGordon JMGordon commented Feb 10, 2018

Moved some of the text around regarding setting up firewall rules on macOS to help
improve text flow.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. tools Issues and PRs related to the tools directory. labels Feb 10, 2018
@daynin
Copy link
Contributor

daynin commented Feb 10, 2018

@JMGordon hi! I think you should check these two options too:

  • documentation is changed or added
  • commit message follows commit guidelines

BUILDING.md Outdated

If the path to your build directory contains a space, the build will likely fail.

After building, you may want to setup [firewall rules](tools/macosx-firewall.sh)
to avoid popups asking to accept incoming network connections when running tests.
Copy link
Member

Choose a reason for hiding this comment

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

nit suggestion:

After building, setting up [filewall rules](tools/macosx-firewall.sh) can avoid popups
asking to accept incoming network connections when running tests.

@jasnell
Copy link
Member

jasnell commented Feb 26, 2018

Looks like tools/remark-cli/package-lock.json was accidentally added to the commit?

BUILDING.md Outdated

If the path to your build directory contains a space, the build will likely fail.

After building, setting up [filewall rules](tools/macosx-firewall.sh) can avoid popups
Copy link
Member

Choose a reason for hiding this comment

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

I'm assuming this was a typo in the suggestion from @jasnell and that this should have remained as firewall rules.

@mmarchini
Copy link
Contributor

@JMGordon would you be so kind and do a rebase to resolve the conflict in BUILDING.md?

@trivikr
Copy link
Member

trivikr commented Mar 26, 2018

ping @JMGordon

@BridgeAR
Copy link
Member

I went ahead and rebased and added a commit that addressed the typo plus a suggested change from myself. So @jasnell PTAL

@BridgeAR
Copy link
Member

@jasnell
Copy link
Member

jasnell commented Apr 10, 2018

still lgtm

trivikr pushed a commit that referenced this pull request Apr 15, 2018
PR-URL: #18689
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
@trivikr
Copy link
Member

trivikr commented Apr 15, 2018

Landed in b003c86

Congratulations @JMGordon for your first commit in Node.js core! 🎉🎉🎉

@trivikr trivikr closed this Apr 15, 2018
jasnell pushed a commit that referenced this pull request Apr 16, 2018
PR-URL: #18689
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
BridgeAR pushed a commit to BridgeAR/node that referenced this pull request May 1, 2018
PR-URL: nodejs#18689
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. tools Issues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.