summary refs log tree commit diff
path: root/CONTRIBUTING.md
AgeCommit message (Collapse)AuthorLines
2023-11-16fix: Update CONTRIBUTING.md recommend -> recommendedZephyr-1/+1
2023-03-30Update contributing links for rustc-dev-guide changesJynn Nelson-1/+0
- Remove unused reference link in CONTRIBUTING.md - Change the contributing_url for triagebot to the getting started page
2022-12-23Link to other resources instead of inlining their informationJoshua Nelson-3/+4
The other places are more accurate and up-to-date. - Link to `std-dev-guide` in CONTRIBUTING.md Thom and Mara said the guide is in reasonably good shape, and it's tailored more closely to people working on the standard library. - Link to CONTRIBUTING.md instead of rustc-dev-guide in the main readme CONTRIBUTING.md has more information and also links the std-dev-guide. - Link to forge for the list of tested platforms; the one in the readme was hopelessly out of date.
2021-11-22Give people a single link they can click in the contributing guideJoshua Nelson-5/+6
Doc Jones mentioned that one of the things making it hard to get started is that the amount of information is overwhelming, between the dev-guide, contributing guide, and discussion platforms. This gives people a single link they can click to ask for help.
2021-03-09Make opening sentence friendlier for new contributorsHenry Boisdequin-1/+7
Co-authored-by: Camelid <camelidcamel@gmail.com>
2021-03-09Update CONTRIBUTING.mdHenry Boisdequin-1/+21
Fixes #77215 As mentioned in #77215, the current CONTRIBUTING.md links to the rustc-dev-guide. Even though the rustc-dev-guide has lots of useful information for contributors, one is already confused by reading the first line of the current CONTRIBUTING.md. > To get started, read the [Getting Started] guide in the [rustc-dev-guide]. This line tells the contributor to go and read the rustc-dev-guide. What is the rustc-dev-guide? What does rustc even mean? These are some of the questions that went into my head when reading this line as a first time contributor. By explaining what the rustc-dev-guide is and some platforms to get help, a new contributor understands what the first step is and the process is much clearer. The `About the [rustc-dev-guide]` section explains what the rustc-dev-guide is, what rustc is, and the purpose out of reading the guide. The `Getting help` section points the user to some places where they can get help, find a mentor, and introduce themsevles.
2020-09-28Link to "Contributing to Rust" rather than "Getting Started".follower-2/+2
Change to link to "Contributing to Rust" chapter of `rustc` Dev Guide, primarily on the basis that the GitHub "first contribution" Issue "pop-up" says "Be sure to review the [contributing guidelines] and [code of conduct]" and links to this file. When/if the guide/"Getting Started" section gets revised to not be `rustc`-specific the linked section can be changed. In the meantime this prevents leading first time contributors into a confusing cul de sac.
2020-07-07Update reference to CONTRIBUTING.mdYuki Okushi-0/+7
2020-07-03Fix "getting started" linkValentin-1/+1
The previous link is 404.
2020-06-17move contributing.md to rustc-dev-guide and point at getting startedmark-524/+3
2020-05-04Rollup merge of #71864 - mibac138:patch-1, r=jonas-schievinkDylan DPC-1/+1
Update link in contributing.md
2020-05-04Rollup merge of #71844 - flip1995:subtree_clippy_doc, r=oli-obkDylan DPC-3/+2
List Clippy as a subtree, instead of a submodule r? @oli-obk
2020-05-04Update link in contributing.mdMichael-1/+1
2020-05-03List Clippy as a subtree, instead of a submoduleflip1995-3/+2
2020-04-28Suggest stage 1 if stage 0 failsDylan MacKenzie-3/+7
2020-04-28Direct contributors to try stage 0 rustdoc firstDylan MacKenzie-4/+8
2020-04-02Address reviewsOliver Scherer-7/+8
2020-04-02Address review commentsOliver Scherer-6/+12
2020-04-01Triple backticksOliver Scherer-2/+8
2020-04-01Explain that you have to specify path and repository during subrepo ↵Oliver Scherer-8/+16
synchronizations
2020-04-01Git subtree is upstream, no need to installOliver Scherer-5/+1
2020-04-01s/subrepo/subtree/Oliver Scherer-16/+16
2020-04-01Explain how to work with subreposOliver Scherer-2/+47
2020-03-12Rollup merge of #69747 - spastorino:rename-rustc-guide, r=pietroalbiniMazdak Farrokhzad-10/+10
Rename rustc guide This is in preparation for https://github.com/rust-lang/rustc-guide/issues/470 Needs to be merged after we actually rename the guide. Have used this to rename: `git grep -l 'rustc_guide' | xargs sed -i 's/rustc_guide/rustc_dev_guide/g'` `git grep -l 'rustc-guide' | xargs sed -i 's/rustc-guide/rustc-dev-guide/g'` `git grep -l 'rustc guide' | xargs sed -i 's/rustc guide/rustc dev guide/g'`
2020-03-10rust-lang.github.io/rustc-dev-guide -> rustc-dev-guide.rust-lang.orgSantiago Pastorino-5/+5
2020-03-10Rename rustc guide to rustc dev guideSantiago Pastorino-2/+2
2020-03-10Rename rustc-guide to rustc-dev-guideSantiago Pastorino-9/+9
2020-03-09update x.py tidy testing commandChris Simpkins-1/+1
2020-01-30[docs] remind bug reporters to update nightlyJacob Rothstein-0/+3
2019-12-26Remove redundant link textsMatthew Kraai-2/+2
2019-11-28Update CONTRIBUTING.mdDylan DPC-1/+1
2019-11-28Update CONTRIBUTING.mdDylan DPC-1/+1
2019-11-27Clarifies how to tag users for assigning PRsMark Lodato-3/+3
2019-11-07Update link on CONTRIBUTING.mdYuki Okushi-1/+1
2019-10-23Rollup merge of #65007 - BO41:keywords, r=nikomatsakisYuki Okushi-0/+8
Mention keyword closing policy closes #59233 / https://github.com/rust-lang/rust/issues/59233#issuecomment-478362693 rewording suggestions welcome > Also in the referenced issue, the commit number of the new commit > that could close that issue is not really informative. The PR number itself appeared in the issue > is more informative and concise. @lzutao what do you mean with that? Is this fixed by the new "May be fixed by #XXXXX"?
2019-10-18Apply suggested wordingBO41-2/+4
to better describe the situation
2019-10-02Fix typoBO41-1/+1
2019-10-02Mention keyword closing policyBO41-0/+6
2019-10-02Replace mentions of IRC with DiscordBO41-4/+3
2019-07-09Update cargo-vendor usageEric Huss-8/+1
2019-03-31Rollup merge of #59234 - stepnivlk:add-no_merge_policy, r=oli-obkMazdak Farrokhzad-0/+7
Mention `no merge policy` in the CONTRIBUTING guide Issue: https://github.com/rust-lang/rust/issues/59233
2019-03-16Mention `no merge policy` in the CONTRIBUTING guidestepnivlk-0/+7
2019-03-14Fix capitalisation problemvarkor-1/+2
2019-03-14Move rollup description earliervarkor-12/+11
2019-03-14Make all references to @bors or users linksvarkor-8/+9
2019-03-14Update r+ syntaxvarkor-2/+2
2019-03-14Add links to @rust-highfive and @borsvarkor-2/+4
2019-03-14Add a link to the Discord and Zulip serversvarkor-1/+3
2019-03-14Remove trailing newlinesvarkor-2/+2
2019-03-14Fix a broken link to the rustc-guidevarkor-0/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2025-10-25 23:07:49 +0000