|
| 1 | +# Bring repository into baseline compliance |
| 2 | + |
| 3 | +## Description |
| 4 | + |
| 5 | +Fix all failing baseline audit checks to bring the repository into compliance. The audit revealed 6 failing checks that need to be addressed. |
| 6 | + |
| 7 | +## Checklist |
| 8 | + |
| 9 | +### Error-level issues (must fix) |
| 10 | + |
| 11 | +- [ ] Fix `.envrc` to use `PATH_add bin` instead of `export PATH="$PWD/bin:$PATH"` |
| 12 | +- [ ] Create `BannedSymbols.txt` in repository root |
| 13 | +- [ ] Add BannedApiAnalyzers configuration to `Directory.Build.props` |
| 14 | +- [ ] Fix dev CLI capabilities JSON trailing comma issue in `tools/dev-cli/dev.cs` |
| 15 | + |
| 16 | +### Warning-level issues (should fix) |
| 17 | + |
| 18 | +- [ ] Add `#region Purpose` annotations to 8 dev-cli files: |
| 19 | + - [ ] `tools/dev-cli/dev.cs` |
| 20 | + - [ ] `tools/dev-cli/endpoints/verify-samples.cs` |
| 21 | + - [ ] `tools/dev-cli/endpoints/build.cs` |
| 22 | + - [ ] `tools/dev-cli/endpoints/self-install.cs` |
| 23 | + - [ ] `tools/dev-cli/endpoints/check-version.cs` |
| 24 | + - [ ] `tools/dev-cli/endpoints/test.cs` |
| 25 | + - [ ] `tools/dev-cli/endpoints/clean.cs` |
| 26 | + - [ ] `tools/dev-cli/endpoints/workflow.cs` |
| 27 | +- [ ] Clean up orphaned CPM packages in `Directory.Packages.props`: |
| 28 | + - [ ] `TimeWarp.Build.Tasks` (version 1.0.0) |
| 29 | + - [ ] `GlobalUsingsAnalyzer` (version 1.4.0) |
| 30 | + - [ ] `Microsoft.CodeAnalysis.CSharp` (version 5.0.0) |
| 31 | + - [ ] `Microsoft.CodeAnalysis.Analyzers` (version 4.14.0) |
| 32 | + |
| 33 | +### Verification |
| 34 | + |
| 35 | +- [ ] Run `ganda repo audit` to verify all checks pass |
| 36 | +- [ ] Commit changes |
| 37 | + |
| 38 | +## Notes |
| 39 | + |
| 40 | +### Audit Results (2026-03-18) |
| 41 | + |
| 42 | +``` |
| 43 | +Passed: 5 | Failed: 6 |
| 44 | +
|
| 45 | +Failing checks: |
| 46 | +1. baseline-envrc (Error) - .envrc does not contain PATH_add bin |
| 47 | +2. baseline-banned-symbols (Error) - BannedSymbols.txt is missing |
| 48 | +3. baseline-banned-api-analyzers (Error) - Directory.Build.props missing BannedApiAnalyzers config |
| 49 | +4. baseline-dev-cli-capabilities (Error) - Capabilities JSON has trailing comma |
| 50 | +5. baseline-region-annotations (Warning) - 8 files missing #region Purpose |
| 51 | +6. baseline-cpm-consistency (Warning) - 4 orphaned PackageVersion entries |
| 52 | +``` |
| 53 | + |
| 54 | +### Passing checks (for reference) |
| 55 | + |
| 56 | +- `baseline-bin-dev` - bin/dev is present |
| 57 | +- `baseline-source-props` - source/Directory.Build.props exists |
| 58 | +- `baseline-msbuild-props` - msbuild/repository.props exists |
| 59 | +- `baseline-directory-packages` - Directory.Packages.props exists |
| 60 | +- `baseline-runfile-variables` - All #:project directives use MSBuild variables |
| 61 | + |
| 62 | +### Related Issue |
| 63 | + |
| 64 | +The NuGet release workflow failed due to workflow name mismatch: |
| 65 | +- Workflow renamed from `ci-cd.yml` to `workflow.yml` |
| 66 | +- NuGet trusted publishing policy still expects `ci-cd.yml` |
| 67 | +- This should be addressed separately (update NuGet policy or rename workflow back) |
0 commit comments