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

doc: fix website wg mislink #4357

Closed
wants to merge 1 commit into from
Closed

doc: fix website wg mislink #4357

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Dec 19, 2015

nodejs/website -> nodejs/nodejs.org

@mscdex mscdex added the doc Issues and PRs related to the documentations. label Dec 19, 2015
@evanlucas
Copy link
Contributor

LGTM

@mscdex
Copy link
Contributor

mscdex commented Dec 19, 2015

Is it possible to change the nodejs/website redirect to nodejs/nodejs.org? Or was that a one-time thing when it was redirected to nodejs/iojs.org?

@ghost
Copy link
Author

ghost commented Dec 19, 2015

@mscdex i believe that's a github thing. the website repository was changed to iojs.org, so github redirected it there. i can try and contact them to ask whether that can be changed though, if you'd like.

@mscdex
Copy link
Contributor

mscdex commented Dec 19, 2015

@sup Yeah, if they are willing to change it again I think that would be ideal.

@ghost
Copy link
Author

ghost commented Dec 19, 2015

@mscdex contacted them, will update on further discussion

@ghost
Copy link
Author

ghost commented Dec 20, 2015

i need confirmation from someone in the TSC, @mscdex, can you give me your email so i can cc you in the discussion? (or someone else from @nodejs/tsc)

@ghost
Copy link
Author

ghost commented Dec 25, 2015

bump, i need an email address from someone on the tsc/ctc to confirm the redirect change

@cjihrig
Copy link
Contributor

cjihrig commented Dec 29, 2015

The change LGTM.

If others are on board with changing the nodejs/website redirect to point to nodejs/nodejs.org, then you can CC me. My email is on my GitHub profile.

@cjihrig
Copy link
Contributor

cjihrig commented Dec 29, 2015

FYI - @sup put me in contact with GitHub support, and I approved the redirect update.

@ghost
Copy link
Author

ghost commented Dec 29, 2015

oh yeah, forgot to report about that - sorry!

@ghost
Copy link
Author

ghost commented Dec 29, 2015

update, redirect is changed! nodejs/website now redirects to this repo, i'll close this PR as well.

@ghost ghost closed this Dec 29, 2015
@mscdex
Copy link
Contributor

mscdex commented Dec 30, 2015

Yay!

rvagg pushed a commit that referenced this pull request Jan 4, 2016
PR-URL: #4357
Reviewed-By: Evan Lucas <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
@rvagg
Copy link
Member

rvagg commented Jan 4, 2016

Even with the redirect we should probably update the doc to point to the correct repo. I've landed this commit @ 7c8efeb with 3 LGTMs, I don't read @mscdex' comments as a -1 for this particular change, I hope that's right (sorry if I've read wrong @mscdex).

I believe this is your first commit to core @sup, thanks for the fix, welcome on board!

Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request Jan 6, 2016
PR-URL: nodejs#4357
Reviewed-By: Evan Lucas <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
PR-URL: nodejs#4357
Reviewed-By: Evan Lucas <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants