43 lines
1.1 KiB
Markdown
43 lines
1.1 KiB
Markdown
# Architecture
|
|
|
|
## Overview
|
|
|
|
This repository uses Forgejo Actions on a `linux-dev` runner to validate customer code and generate project analysis reports.
|
|
|
|
Green workflow:
|
|
Automation completed and reports were generated.
|
|
|
|
Red workflow:
|
|
Automation itself failed, crashed, or required reports were not produced.
|
|
|
|
## Components
|
|
|
|
- Forgejo workflows
|
|
- `linux-dev` runner
|
|
- `tools/validate-code.sh`
|
|
- `tools/project-report.sh`
|
|
- customer source files
|
|
- generated markdown reports
|
|
- future deployment automation, kept separate from debugging automation
|
|
|
|
## Text Diagram
|
|
|
|
```text
|
|
Customer Push / Pull Request
|
|
|
|
|
v
|
|
Forgejo Workflow
|
|
|
|
|
+--> validate.yml --> tools/validate-code.sh --> reports/errors.md
|
|
|
|
|
+--> project-report.yml --> tools/validate-code.sh
|
|
tools/project-report.sh
|
|
--> reports/*.md
|
|
|
|
|
v
|
|
Forgejo Logs print summaries and report excerpts
|
|
```
|
|
|
|
## Future Direction
|
|
|
|
Later deployment automation may choose to block releases when errors are found. That is intentionally separate from the current DevPlus1 debugging behavior.
|