6 Commits

Author SHA1 Message Date
Abhinav Gupta
0dcebfb72b error strings: Don't capitalize, use periods, or newlines
Per [Go Code Review Comments][1],

> Error strings should not be capitalized (unless beginning with proper
> nouns or acronyms) or end with punctuation

staticcheck's [ST1005][2] also complains about these. For example,

```
object_walker.go:63:10: error strings should not be capitalized (ST1005)
object_walker.go:101:10: error strings should not be capitalized (ST1005)
object_walker.go:101:10: error strings should not end with punctuation or a newline (ST1005)
plumbing/format/commitgraph/file.go:17:26: error strings should not be capitalized (ST1005)
```

This fixes all instances of this issue reported by staticcheck.

  [1]: https://github.com/golang/go/wiki/CodeReviewComments#error-strings
  [2]: https://staticcheck.io/docs/checks/#ST1005
2021-12-04 15:40:53 -08:00
Máximo Cuadros
2bdfd91f04 *: migration from gopkg to go modules 2020-03-10 00:40:56 +01:00
Oleksandr Redko
81627ab53e Fix typos in comments, variables and function names
Signed-off-by: Oleksandr Redko <oleksandr.red+github@gmail.com>
2019-10-24 23:37:27 +03:00
Chris Marchesi
1000bc0ef8 git: Add Tag objects to the list of supported objects for walking
This is necessary to support pruning on Tag objects.

Signed-off-by: Chris Marchesi <chrism@vancluevertech.com>
2018-09-07 09:00:42 -07:00
ferhat elmas
9a9f35269c *: simplication
- no unnecessary err/bool check, uses them directly

Signed-off-by: ferhat elmas <elmas.ferhat@gmail.com>
2017-12-18 02:09:00 +01:00
Taru Karttunen
f28e4477df Make prune object walker generic 2017-11-29 11:01:41 -08:00