Commit 0958291
authored
fix(reno): Do not use sparse-checkout with reno (#46061)
### What does this PR do?
Removes `sparse-checkout` from the `release-note-check` job in the `label-analysis` workflow.
`sparse-checkout` causes Git to set `extensions.worktreeConfig = true` in `.git/config`. `reno` uses `dulwich` (a Python Git library) which doesn't support that extension, resulting in:
```
dulwich.repo.UnsupportedExtension: b'worktreeConfig'
```
See https://github.com/DataDog/datadog-agent/actions/runs/21820574446/job/62952555264?pr=46059 for a failed run example.
### Motivation
The `release-note-check` job has been failing on all PRs since #45330 was merged.
### Describe how you validated your changes
- Reproduced the error locally by enabling `sparse-checkout` and running `reno lint`
- Confirmed the error disappears once `sparse-checkout` (and its `extensions.worktreeConfig` side effect) is removed
### Additional Notes
`sparse-checkout` is not needed for this job because:
- It checks out `ref: main` (trusted code), not PR code
- It already uses `fetch-depth: 0` for full git history (needed by reno)
- PR-specific releasenotes are safely fetched separately via `git checkout FETCH_HEAD -- releasenotes ...`
Co-authored-by: nicolas.schweitzer <nicolas.schweitzer@datadoghq.com>1 parent 81c0489 commit 0958291
1 file changed
Lines changed: 2 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
| 22 | + | |
| 23 | + | |
22 | 24 | | |
23 | 25 | | |
24 | 26 | | |
25 | 27 | | |
26 | 28 | | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | 29 | | |
32 | 30 | | |
33 | 31 | | |
| |||
0 commit comments