From 93128efef8a7577a8e6cc6d2ce17099420dd22a5 Mon Sep 17 00:00:00 2001 From: Jonas Schievink Date: Thu, 15 Apr 2021 19:45:07 +0200 Subject: Fix markdown links --- docs/dev/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/dev') diff --git a/docs/dev/README.md b/docs/dev/README.md index f74f7d8eb..d0e6d29d8 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -235,14 +235,14 @@ We don't do "patch" releases, unless something truly egregious comes up. There are three sets of people with extra permissions: -* rust-analyzer GitHub organization (**admins**)[https://github.com/orgs/rust-analyzer/people?query=role:owner] (which include current t-compiler leads). +* rust-analyzer GitHub organization [**admins**](https://github.com/orgs/rust-analyzer/people?query=role:owner) (which include current t-compiler leads). Admins have full access to the org. -* (**review**)[https://github.com/orgs/rust-analyzer/teams/review] team in the organization. +* [**review**](https://github.com/orgs/rust-analyzer/teams/review) team in the organization. Reviewers have `r+` access to all of organization's repositories and publish rights on crates.io. They also have direct commit access, but all changes should via bors queue. It's ok to self-approve if you think you know what you are doing! bors should automatically sync the permissions. -* (**triage**)[https://github.com/orgs/rust-analyzer/teams/triage] team in the organization. +* [**triage**](https://github.com/orgs/rust-analyzer/teams/triage) team in the organization. This team can label and close issues. Note that at the time being you need to be a member of the org yourself to view the links. -- cgit v1.2.3