fortress-rollback/.gitignore at main · wallstop/fortress-rollback · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
# Generated by Cargo
# will have compiled files and executables
/target/

# Cargo.lock is committed for reproducible CI/CD builds
# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html

# These are backup files generated by rustfmt
**/*.rs.bk

.claude/**
.nanocoder/**
.idea/**

site/
.tmp/

*.zip

.vscode/**

PLAN.md
*TTrace*
actionlint

# Added by cargo

/target

job-logs.txt

net.rs
game.rs

# Added by cargo
#
# already existing elements were commented out

#/target
#Cargo.lock


specs/tla/states**
specs/tla/*_test.cfg
specs/**/*.bin
specs/**/*Rollback_TTrace_*
states/**
*.z3-trace
states.dot

# TLA+ tools cache: `tla2tools.jar` is a multi-megabyte binary fetched at runtime
# by `scripts/verification/verify-tla.sh` and `.devcontainer/setup-tla-tools.sh`;
# `.version` is a generated sentinel tracking which jar revision is cached. The
# pinned upstream version lives in the tracked `.tla-tools-version` file at the
# repo root — that is the single source of truth. Committing anything under
# `.tla-tools/` causes drift between the sentinel and the actual cached jar.
.tla-tools/

loom-tests/target/**
mutants.out/**
progress/**
/tests/simulation/corpus/**/.candidate.*
/tests/simulation/corpus/**/.promotion.lock/
# Lychee link checker cache
.lycheecache

# Python bytecode cache
__pycache__/

# Node.js artifacts (from npm tools like markdownlint-cli)
package-lock.json
package.json
node_modules/
*.pyc
*.pyo

pre-commit.txt
pre-commit.log
pre-push.txt
pre-push.log
pr-description.md
text_tt*
proposed_fix
ci-log*.txt
ci-log*.log
N-PLAYER-DESYNC-AUDIT.md
GOAL.md