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
Guidance for AI coding tools working on this project.
@README.md
@docs/getting-started.md
@docs/architecture.md
```bash
cargo build --release
cargo test
cargo check
cargo clippy
cargo clippy --features gui-win32 --target x86_64-pc-windows-gnu
cargo fmt
installrs --target ./my-installer --output installer
INSTALLRS_LOCAL_PATH=1 installrs --target ./my-installer --output installer
installrs --target ./my-installer -v # debug
installrs --target ./my-installer -vv # trace
```
When you change code that affects how someone uses or understands
InstallRS, update README.md and/or the relevant doc files in `docs/`.
Make sure to update documentation indexes and links.
If you add a new doc file, add it to any relevant indexes
and link to it from the README and any relevant "See also" doc sections.
Also update `CHANGELOG.md` with a brief high-level overview note about the change.
Keep changelog entries concise (1-2 lines) and focused on the user-facing impact;
don't include internal implementation details or development notes.
Don't add changelog entries for changes that are purely internal
and don't affect users of the library or CLI.