@@ -10,11 +10,9 @@ So, before sending a CL, please please please:
10
10
exist already. This allows us to identify redundant requests, or to
11
11
merge a specific problem into a more general one, and to assess the
12
12
importance of the problem.
13
-
14
13
- ** claim it for yourself** by commenting on the issue or, if you are
15
14
able, by assigning the issue to yourself. This helps us avoid two
16
15
people working on the same problem.
17
-
18
16
- ** propose an implementation plan** in the issue tracker for CLs of
19
17
any complexity. It is much more efficient to discuss the plan at a
20
18
high level before we start getting bogged down in the details of
@@ -41,7 +39,7 @@ for example by making the code self-explanatory.
41
39
It's fine to disagree with a comment,
42
40
point out a reviewer's mistake,
43
41
or 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.
45
43
But please don't dismiss or quietly ignore a comment without action,
46
44
as it may lead reviewers to repeat themselves,
47
45
or to serious problems being neglected.
@@ -60,8 +58,10 @@ claiming it.
60
58
61
59
## Getting started
62
60
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.
65
65
66
66
## Build
67
67
0 commit comments