fix(workflows): resolve git revision error in KB lint workflow

- Fix HEAD~1...HEAD error for shallow clones by using github.event.before/after
- Add proper error suppression with 2>/dev/null
- Add fallback logic for edge cases (initial commits, force pushes)
- Archive resolved runner setup issue to docs/issues/archive/resolved/
- Add archive documentation and next steps guide

Fixes workflow execution on test/runner-validation branch.
Resolves issue with 'fatal: bad revision' error in logs.
This commit is contained in:
Gitea Actions
2025-11-11 14:46:26 -07:00
parent 72d74f86ad
commit 1423ee1f04
4 changed files with 209 additions and 4 deletions

View File

@@ -0,0 +1,31 @@
# Issues Archive
This folder contains archived issues that have been resolved or are no longer active.
## Structure
- **`resolved/`** - Issues that have been resolved and documented
- Future categories can be added as needed (e.g., `duplicate/`, `wontfix/`, `invalid/`)
## Archive Process
When an issue is resolved:
1. Update the issue file with a "Resolution" section
2. Change status from `captured` to `resolved`
3. Add resolution date
4. Document what was fixed and how
5. Move the file to `archive/resolved/`
## Purpose
- Keep active issues visible in the main `docs/issues/` folder
- Maintain historical record of resolved issues
- Allow for easy reference to past solutions
- Support project documentation and knowledge retention
---
**Location**: `docs/issues/archive/`
**Related**: `docs/issues/README.md` - Main issues capture system