github.com/grafana/nanogit v1.7.5
Legitimate Grafana Git library
Basename is uppercase README.mdCaret or XOR operation token in source
SHA-2560048628ba67f860a9ba57384d26c648b74ba582fe31fde42c9361160302ce195
Evidence
108:31… d edge cases
109- Keep documentation up to date with code changes
110
111# Security
112- Never log sensitive information (tokens, passwords)
113- Validate all input parameters
114- Use secure defaults
115- Follow security b …
1## What
2<!-- Describe the changes in this PR -->
3
4## Why
5<!-- Explain the motivation behind these changes -->
6
7## How
8<!-- Describe how these changes were implemented -->
9
10## Remarks
11<!-- Any additional notes, considerations, or potential impacts -->
12
13## Author Checklist
14- [ ] Tests added/updated.
15- [ ] Documentation updated.
16- [ ] Changes have been tested locally.
⋯10 lines
11 "github.com/grafana/nanogit/perf"
12 ],
13 "packageRules": [
14 {
15 "matchDatasources": [
⋯10 lines
10:22… cies are up to date
11 - go mod download
12 - go work vendor
13
14builds:
15 - id: nanogit-cli
16 main: ./cli/cmd/nanogit
⋯8 lines
⋯7 lines
51### Commit Message Convention
52
53We use [Conventional Commits](https://www.conventionalcommits.org/) to automate versioning and changelog generation. Each commit message must follow this format:
54
55``` …
Showing the top 5 files — 4 more files (29 regions) not shown.