@@ -10,11 +10,9 @@ So, before sending a CL, please please please:
1010 exist already. This allows us to identify redundant requests, or to
1111 merge a specific problem into a more general one, and to assess the
1212 importance of the problem.
13-
1413- ** claim it for yourself** by commenting on the issue or, if you are
1514 able, by assigning the issue to yourself. This helps us avoid two
1615 people working on the same problem.
17-
1816- ** propose an implementation plan** in the issue tracker for CLs of
1917 any complexity. It is much more efficient to discuss the plan at a
2018 high level before we start getting bogged down in the details of
@@ -41,7 +39,7 @@ for example by making the code self-explanatory.
4139It's fine to disagree with a comment,
4240point out a reviewer's mistake,
4341or offer to address a comment in a follow-up change,
44- leaving a TODO comment in the current CL.
42+ leaving a ` TODO ` comment in the current CL.
4543But please don't dismiss or quietly ignore a comment without action,
4644as it may lead reviewers to repeat themselves,
4745or to serious problems being neglected.
@@ -60,8 +58,10 @@ claiming it.
6058
6159## Getting started
6260
63- Most of the ` gopls ` logic is in the ` golang.org/x/tools/gopls/internal `
64- directory. See [ design/implementation.md] ( ./design/implementation.md ) for an overview of the code organization.
61+ [ ![ PkgGoDev] ( https://pkg.go.dev/badge/golang.org/x/tools/gopls/internal )] ( https://pkg.go.dev/golang.org/x/tools/gopls/internal )
62+
63+ Most of the ` gopls ` logic is in the ` golang.org/x/tools/gopls/internal ` directory.
64+ See [ design/implementation.md] ( ./design/implementation.md ) for an overview of the code organization.
6565
6666## Build
6767
0 commit comments