Fix wrong option in example

[rndmh3ro]

No description provided.

[greptile-apps]

Greptile Summary

This PR fixes two related issues in the ansible-galaxy provider example in docs/dev-tools/prepare.md:

• Wrong flag corrected: -f (force) was replaced with -r (requirements file). In ansible-galaxy, -r is the correct flag to specify a requirements file; -f means "force reinstall" and would not pass the file path correctly.
• Missing output artifact creation added: && touch .galaxy-installed was appended so that the .galaxy-installed file declared in outputs = [\".galaxy-installed\"] is actually created on success. Without this, mise prepare would never see the output and would re-run the provider on every invocation.

Confidence Score: 5/5

Safe to merge — purely a documentation fix correcting a wrong CLI flag and a missing output artifact step.

Single-file documentation-only change with two clearly correct fixes: wrong ansible-galaxy flag (-f → -r) and missing touch to satisfy the declared output. No logic, code, or behaviour changed.

No files require special attention.

Important Files Changed

Filename	Overview
docs/dev-tools/prepare.md	Documentation fix: corrects ansible-galaxy install flag from -f (force) to -r (requirements file), and adds && touch .galaxy-installed to properly create the declared output artifact

Sequence Diagram

sequenceDiagram
    participant mise
    participant ansible-galaxy

    mise->>ansible-galaxy: ansible-galaxy install -r requirements.yml
    ansible-galaxy-->>mise: installs roles from requirements.yml
    mise->>mise: touch .galaxy-installed (creates output artifact)
    Note over mise: outputs=[".galaxy-installed"] check passes
    mise-->>mise: provider marked complete

Loading

_{Reviews (2): Last reviewed commit: "Update docs/dev-tools/prepare.md" | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request updates the documentation for dev-tools to use the correct flag for installing Ansible Galaxy requirements. A review comment points out that the example command needs to create a marker file to satisfy the defined output requirement, preventing unnecessary re-executions by the build tool.