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

Fixing Rust Moderation Team link in Code of Conduct #46939

Merged
merged 1 commit into from
Dec 26, 2017

Conversation

davidalber
Copy link
Contributor

The Code of Conduct has two broken links to the Rust Moderation Team.

@kennytm
Copy link
Member

kennytm commented Dec 22, 2017

Thanks!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Dec 22, 2017

📌 Commit 4e14a7d has been approved by kennytm

@kennytm kennytm added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Dec 22, 2017
kennytm added a commit to kennytm/rust that referenced this pull request Dec 23, 2017
…-link, r=kennytm

Fixing Rust Moderation Team link in Code of Conduct

The [Code of Conduct](https://github.com/rust-lang/rust/blob/master/CODE_OF_CONDUCT.md) has two broken links to the Rust Moderation Team.
- The current link is https://github.com/rust-lang/rust/blob/master/team.html#Moderation. That happened because the link is relative.
- The link in this PR is https://www.rust-lang.org/team.html#Moderation-team. Note: at the moment this is redirected client-side to a language-specific page and loses the fragment identifier. rust-lang/prev.rust-lang.org#992 aims to correct that.
kennytm added a commit to kennytm/rust that referenced this pull request Dec 23, 2017
…-link, r=kennytm

Fixing Rust Moderation Team link in Code of Conduct

The [Code of Conduct](https://github.com/rust-lang/rust/blob/master/CODE_OF_CONDUCT.md) has two broken links to the Rust Moderation Team.
- The current link is https://github.com/rust-lang/rust/blob/master/team.html#Moderation. That happened because the link is relative.
- The link in this PR is https://www.rust-lang.org/team.html#Moderation-team. Note: at the moment this is redirected client-side to a language-specific page and loses the fragment identifier. rust-lang/prev.rust-lang.org#992 aims to correct that.
@bors
Copy link
Contributor

bors commented Dec 25, 2017

⌛ Testing commit 4e14a7d with merge c7a76dcf8d0b4dd95b5dd3ed0f9d42c62bee219e...

@bors
Copy link
Contributor

bors commented Dec 25, 2017

💔 Test failed - status-travis

@kennytm
Copy link
Member

kennytm commented Dec 25, 2017

@bors retry #47002

@bors
Copy link
Contributor

bors commented Dec 26, 2017

⌛ Testing commit 4e14a7d with merge 3be6382b49ea6885ea2d0aa40161f4e16b8bac24...

@bors
Copy link
Contributor

bors commented Dec 26, 2017

💔 Test failed - status-travis

kennytm added a commit to kennytm/rust that referenced this pull request Dec 26, 2017
…-link, r=kennytm

Fixing Rust Moderation Team link in Code of Conduct

The [Code of Conduct](https://github.com/rust-lang/rust/blob/master/CODE_OF_CONDUCT.md) has two broken links to the Rust Moderation Team.
- The current link is https://github.com/rust-lang/rust/blob/master/team.html#Moderation. That happened because the link is relative.
- The link in this PR is https://www.rust-lang.org/team.html#Moderation-team. Note: at the moment this is redirected client-side to a language-specific page and loses the fragment identifier. rust-lang/prev.rust-lang.org#992 aims to correct that.
bors added a commit that referenced this pull request Dec 26, 2017
Rollup of 8 pull requests

- Successful merges: #46928, #46930, #46933, #46939, #46940, #46943, #46979, #46986
- Failed merges:
@bors bors merged commit 4e14a7d into rust-lang:master Dec 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants