Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/build.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,13 @@ jobs:
run: |
dotnet test ./src/log4net.sln

# Pester 5.9 ships on all three runner images, so nothing is installed here.
- name: Release script tests
shell: pwsh
run: |
$result = Invoke-Pester ./scripts/verify-release.Tests.ps1 -Output Detailed -PassThru
if ($result.FailedCount -ne 0) { exit 1 }

# Runs the same probes twice, JIT compiled and published with Native AOT, so that a
# difference between the two is caused by AOT rather than by the platform. The project
# knows which probes are expected to fail in each mode and exits non-zero when reality
Expand Down
14 changes: 0 additions & 14 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -240,20 +240,6 @@ validate

/.claude/settings.local.json
/.claude/settings.json
/graphify-out/cache
/graphify-out/cost.json
/graphify-out/.graphify_detect.json
/graphify-out/.graphify_ast.json
/graphify-out/.graphify_semantic.json
/graphify-out/.graphify_extract.json
/graphify-out/.graphify_analysis.json
/graphify-out/.graphify_labels.json
/graphify-out/GRAPH_REPORT.md
/graphify-out/graph.html
/graphify-out/.graphify_root
/graphify-out/.graphify_python
/graphify-out/*.sig
/graphify-out/20*

# output of the AOT probe step
/aot-probes/
10 changes: 0 additions & 10 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,6 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co

See [AGENTS.md](AGENTS.md) for the threat model and security boundaries.

## graphify

This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.

Rules:
- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).

## C# code style

Derived from `.editorconfig`, `src/Directory.Build.props`, `src/log4net.globalconfig` and the
Expand Down
Loading
Loading