Merge pull request #946 from Kobzol/remove-master-dependency

Replace hardcoded references to master

Author: Kobzol

src/archive/release-history.md

@@ -96,31 +96,31 @@ older key][pre-0.5-key]).
 - [Release notes][1.3.0-notes]
 
 [1.3.0-announce]: http://blog.rust-lang.org/2015/09/17/Rust-1.3.html
-[1.3.0-notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-130-september-2015
+[1.3.0-notes]: https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#version-130-september-2015
 
 ## 1.2.0
 
 - [Announcement][1.2.0-announce]
 - [Release notes][1.2.0-notes]
 
 [1.2.0-announce]: http://blog.rust-lang.org/2015/08/06/Rust-1.2.html
-[1.2.0-notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-120-2015-08-07
+[1.2.0-notes]: https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#version-120-2015-08-07
 
 ## 1.1.0
 
 - [Announcement][1.1.0-announce]
 - [Release notes][1.1.0-notes]
 
 [1.1.0-announce]: http://blog.rust-lang.org/2015/06/25/Rust-1.1.html
-[1.1.0-notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-110-2015-06-25
+[1.1.0-notes]: https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#version-110-2015-06-25
 
 ## 1.0.0
 
 - [Announcement][1.0.0-announce]
 - [Release notes][1.0.0-notes]
 
 [1.0.0-announce]: http://blog.rust-lang.org/2015/05/15/Rust-1.0.html
-[1.0.0-notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-100-2015-05-15
+[1.0.0-notes]: https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#version-100-2015-05-15
 
 ## 1.0.0-beta
 

src/compiler/backports.md

@@ -72,7 +72,7 @@ The [release team](../release/index.md) (`T-release`) will handle the backport a
 current development cycle (see [release backporting](../release/backporting.md)). If a beta backport
 nomination is approved too late, the release team may be unable to backport the change.
 
-Most of the time, accepted backports target the `master` branch. In rare circumstances, a beta
+Most of the time, accepted backports target the default branch. In rare circumstances, a beta
 backport may need to *directly* target the `beta` branch. In this case, coordinate with the release
 team before merging, by opening a new thread on the Zulip [#t-release
 channel](https://rust-lang.zulipchat.com/#narrow/channel/241545-t-release)).

src/compiler/third-party-out-of-tree.md

@@ -102,7 +102,7 @@ should be labelled appropriately (eg. `relnotes`, `t-compiler`, `t-lang`) just a
 were implemented in `rust-lang/rust` directly, include a description of the changes when it is not
 obvious to those unfamiliar with the compiler or the out-of-tree crate.
 
-[licenses]: https://github.com/rust-lang/rust/blob/master/src/tools/tidy/src/deps.rs#L10-L19
+[licenses]: https://github.com/rust-lang/rust/blob/HEAD/src/tools/tidy/src/deps.rs#L10-L19
 [guide_issue]: https://github.com/rust-lang/rustc-dev-guide/issues/285
 
 ---
@@ -135,10 +135,10 @@ In summary, the process for establishing an out-of-tree crate is as follows:
 1. Add the crate as a dependency to the appropriate in-tree crate and start using.
 
 [gitignore]: https://gitignore.io/api/vim,rust,emacs,clion,visualstudio,visualstudiocode
-[triagebot]: https://github.com/rust-lang/rust/blob/master/triagebot.toml
-[apache]: https://github.com/rust-lang/rust/blob/master/LICENSE-APACHE
+[triagebot]: https://github.com/rust-lang/rust/blob/HEAD/triagebot.toml
+[apache]: https://github.com/rust-lang/rust/blob/HEAD/LICENSE-APACHE
 [coc]: https://www.rust-lang.org/policies/code-of-conduct
-[mit]: https://github.com/rust-lang/rust/blob/master/LICENSE-MIT
+[mit]: https://github.com/rust-lang/rust/blob/HEAD/LICENSE-MIT
 
 ## Third-party crates
 It is sometimes desirable to use the functionality of an existing third-party crate in the compiler.

src/compiler/working-areas.md

@@ -30,15 +30,15 @@ Traits                           | Improving the trait-system design + implement
 
 [Weekly, in Zulip]: #meeting-calendar
 [Polonius]: https://github.com/rust-lang/polonius
-[rustc]: https://github.com/rust-lang/rust/tree/master/compiler
+[rustc]: https://github.com/rust-lang/rust/tree/HEAD/compiler
 [async-await_stream]: https://rust-lang.zulipchat.com/#narrow/channel/187312-wg-async
 [async-await_code]: https://github.com/rust-lang/wg-async-foundations
 [diagnostics_stream]: https://rust-lang.zulipchat.com/#narrow/channel/147480-t-compiler.2Fdiagnostics
 [llvm_stream]: https://rust-lang.zulipchat.com/#narrow/stream/187780-t-compiler.2Fwg-llvm
 [llvm_code]: https://github.com/rust-lang/llvm-project
 [meta_stream]: https://rust-lang.zulipchat.com/#narrow/channel/185694-z-archived-t-compiler.2Fwg-meta
 [mir-opts-stream]: https://rust-lang.zulipchat.com/#narrow/stream/189540-t-compiler.2Fwg-mir-opt
-[mir_transform_code]: https://github.com/rust-lang/rust/tree/master/compiler/rustc_mir_transform
+[mir_transform_code]: https://github.com/rust-lang/rust/tree/HEAD/compiler/rustc_mir_transform
 [nll_stream]: https://rust-lang.zulipchat.com/#narrow/channel/122657-z-archived-t-compiler.2Fwg-nll
 [parallel-rustc_stream]: https://rust-lang.zulipchat.com/#narrow/stream/187679-t-compiler.2Fwg-parallel-rustc
 [pgo_stream]: https://rust-lang.zulipchat.com/#narrow/channel/187830-z-archived-t-compiler.2Fwg-profile-guided-optimization
@@ -57,8 +57,8 @@ Traits                           | Improving the trait-system design + implement
 [borrowck]: https://github.com/rust-lang/rust/tree/ae9173d7dd4a31806c950c90dcc331f1508b4d17/compiler/rustc_borrowck
 [ra-repo]: https://github.com/rust-analyzer/rust-analyzer
 [rustc-dev-guide-repo]: https://github.com/rust-lang/rustc-dev-guide
-[rustc_errors]: https://github.com/rust-lang/rust/tree/master/compiler/rustc_errors
-[rustc_lint]: https://github.com/rust-lang/rust/tree/master/compiler/rustc_lint
+[rustc_errors]: https://github.com/rust-lang/rust/tree/HEAD/compiler/rustc_errors
+[rustc_lint]: https://github.com/rust-lang/rust/tree/HEAD/compiler/rustc_lint
 [annotate-snippets]: https://crates.io/crates/annotate-snippets
 [#wg-autodiff]: https://rust-lang.zulipchat.com/#narrow/channel/390790-wg-autodiff
 [enzyme-project-goal]: https://github.com/rust-lang/rust-project-goals/issues/109

src/infra/docs/bors/queue-resync.md

@@ -20,7 +20,7 @@ the tree.
 
 Sometimes you have to do a bors queue sync for various reasons. This is not
 trivial and requires you to be very careful, as otherwise we may accidentally
-merge PRs to `master` (or even `beta`) that should not have been merged
+merge PRs to the default branch (or even `beta`) that should not have been merged
 otherwise.
 
 ## Steps

src/infra/docs/rustc-ci.md

@@ -1,6 +1,6 @@
 # How the Rust CI works
 
-Continuous integration (CI) workflows on the `rust-lang/rust` repository ensure that the `master` branch
+Continuous integration (CI) workflows on the `rust-lang/rust` repository ensure that the default branch
 is always in a valid state.
 
 The CI infrastructure is described in detail in the [rustc-dev-guide][rustc-dev-guide].

src/infra/toolstate.md

@@ -39,7 +39,7 @@ rules are for when which tools are (not) allowed to break.
 
 * For all tools except for "nightly only" tools, the following extra rules are applied:
     * If a PR lands on the `beta` or `stable` branch, the tool has to be `test-pass`.
-    * If a PR lands on `master` in the week before the beta is cut, and that PR
+    * If a PR lands on the default branch in the week before the beta is cut, and that PR
       regresses the tool (if it makes the state "worse"), CI fails. This is to
       help make sure all these tools become `test-pass` so that a beta can be
       cut. (See the [Forge index][forge] for when the next beta cutoff is
@@ -55,7 +55,7 @@ runs on the `auto` branch (where bors moves a PR to test if it is good for
 integration), the "tool" runners for the individual platforms (at the time of
 writing, Linux and Windows) each submit a JSON file to the repository recording
 the state of each tool for the commit they are testing. Later, if that commit
-actually entirely passed CI and bors moves it to the `master` branch, the
+actually entirely passed CI and bors moves it to the default branch, the
 "current tool status" in the toolstate repository is updated appropriately.
 
 These scripts also automatically ping some people and create issues when tools
@@ -100,8 +100,8 @@ To add a new tool to be tracked, the following steps must be taken:
 4. Submit a PR to the [toolstate repository] to manually add the tool to the
    [`latest.json`] file.
 
-[`checktools.sh`]: https://github.com/rust-lang/rust/blob/master/src/ci/docker/x86_64-gnu-tools/checktools.sh
-[`publish_toolstate.py`]: https://github.com/rust-lang/rust/blob/master/src/tools/publish_toolstate.py
+[`checktools.sh`]: https://github.com/rust-lang/rust/blob/HEAD/src/ci/docker/x86_64-gnu-tools/checktools.sh
+[`publish_toolstate.py`]: https://github.com/rust-lang/rust/blob/HEAD/src/tools/publish_toolstate.py
 [`latest.json`]: https://github.com/rust-lang-nursery/rust-toolstate/blob/master/_data/latest.json
 [Book]: https://doc.rust-lang.org/book/
 [Reference]: https://doc.rust-lang.org/reference/

src/libs/maintaining-std.md

@@ -291,7 +291,7 @@ Changes to hot code might impact performance in consumers, for better or for wor
 
 ### Is the commit log tidy?
 
-PRs shouldn’t have merge commits in them. If they become out of date with `master` then they need to be rebased.
+PRs shouldn’t have merge commits in them. If they become out of date with the default branch then they need to be rebased.
 
 ## Merging PRs
 

src/release/issue-triaging.md

@@ -61,7 +61,7 @@ To do the initial triage and remove the `needs-triage` label, the following cond
 
 ### Applying and removing labels
 
-Users without write access to [`rust-lang/rust`] can use **@rustbot** to add or remove [the labels allowed by the `triagebot.toml` configuration](https://github.com/rust-lang/rust/blob/master/triagebot.toml) as a workaround.
+Users without write access to [`rust-lang/rust`] can use **@rustbot** to add or remove [the labels allowed by the `triagebot.toml` configuration](https://github.com/rust-lang/rust/blob/HEAD/triagebot.toml) as a workaround.
 
 Users with write access should change the labels directly to avoid sending a notification to everyone subscribed to the issue unnecessarily.
 
@@ -73,7 +73,7 @@ For example:
 
 To see a list of all labels, check out the "labels" page next to the search bar in the issue tracker.
 
-Note that some labels may only be applied by users with write access to [`rust-lang/rust`]. Refer to the `allow-unauthenticated` list under `[relabel]` section in [`triagebot.toml`](https://github.com/rust-lang/rust/blob/master/triagebot.toml) to see what labels users without write access may use.
+Note that some labels may only be applied by users with write access to [`rust-lang/rust`]. Refer to the `allow-unauthenticated` list under `[relabel]` section in [`triagebot.toml`](https://github.com/rust-lang/rust/blob/HEAD/triagebot.toml) to see what labels users without write access may use.
 
 ### Relnotes triage
 

src/release/process.md

@@ -60,7 +60,7 @@ following changes:
   - If the release notes PR was merged:
 
     ```console
-    git checkout origin/master -- RELEASES.md
+    git checkout origin/HEAD -- RELEASES.md
     ```
 
   - Otherwise, manually copy `RELEASES.md` from the pending release notes PR
@@ -113,18 +113,18 @@ After the `stable` PR is merged you'll need to start the pre-release. Run this c
 
 You need to replace `YYYY-MM-DD` with the date of the release (Thursday).
 
-## Master bootstrap update (Tuesday)
+## Default branch bootstrap update (Tuesday)
 
 This step can only be done after the new beta has been released. The release
 process for the beta happens automatically at 00:00 UTC every day, so if the
 beta PR landed after that you will have to wait another day. You can check
 whether beta has been released by installing it with rustup.
 
-Send a PR to the master branch to:
+Send a PR to the default branch to:
 
 - Cherry pick the commit that ran `replace-version-placeholder`
   from the now merged beta branch PR. Do not re-run the tool as there might
-  have been other stabilizations on master which were not included in the
+  have been other stabilizations on the default branch which were not included in the
   branched beta, so may not be attributed to the current release.
 
 - Run this to update the bootstrap compiler to the beta you created yesterday:
@@ -151,7 +151,7 @@ Send a PR to the master branch to:
   - Replace any `#[cfg_attr(not(bootstrap), $attr)]` with `#[$attr]`.
 
   Note that if a PR adds `cfg(bootstrap)` and is merged between the beta PR and
-  the master bootstrap update, the `rg` invocation will show them even though
+  the default branch bootstrap update, the `rg` invocation will show them even though
   they won't have to be removed. The easiest way to handle this is to change
   them anyway and let CI show you the failure.