wip: test greptile ignore behavior DEV-2195

[Akuukis]

💭 Notes

Greptile is configured to ignore PRs with a llm-ignore label.
Let's do an experiment how that exactly works.

Conclusion: Greptile fails to un-ignore in any way. All the three 🔴 below seems like a bug. Reported.

👀 Preview steps

1. create a PR with llm-ignore already set before creating it
2. 🟢 notice that Greptile does NOT auto-run
3. write a comment tagging @greptileai
4. 🟢 notice that Greptile does run as requested
5. wait for Greptile to finish it's review ^
6. push second commit
7. 🟢 notice that Greptile does NOT auto-run
8. remove llm-ignore label
9. 🔴 notice that Greptile does NOT trigger on label removal
10. push third commit
11. 🔴 notice that Greptile does NOT auto-run
12. write a comment tagging @greptileai
13. 🟢 notice that Greptile does run as requested
14. push fourth commit
15. 🔴 notice that Greptile does NOT auto-run

[Akuukis]

@greptileai review

[greptile-apps]

Greptile Summary

This is a test PR experimenting with Greptile's llm-ignore label behavior, making only documentation changes to README.md. The changes include a blank-line cosmetic fix, a list marker style switch from - to * for the API docs section, and test artifact content at the bottom of the file.

• The *** / "Hello Greptile!" block appended to the README (lines 83–87) is a test artifact with no value in production documentation; it should be removed before any merge.
• The list marker change (- → *) is otherwise harmless, though it introduces inconsistency with the rest of the file's existing - style bullet lists.

Confidence Score: 5/5

This PR is safe to not merge — it is an intentional test experiment touching only README.md with no production code changes.

The only changes are to README.md: a blank line, a list-marker style switch, and test artifact text appended at the end. No logic, data, or runtime behavior is affected. The test content should not be merged as-is.

README.md — contains test artifact text ("Hello Greptile! 👋" / "This is the third commit.") that must be removed before any merge.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Create PR with llm-ignore label] --> B{Auto-run?}
    B -- No --> C[Manual @greptileai mention]
    C --> D[Greptile runs on request]
    D --> E[Push second commit]
    E --> F{Auto-run?}
    F -- No --> G[Remove llm-ignore label]
    G --> H{Trigger on label removal?}
    H -- No --> I[Push third commit]
    I --> J{Auto-run?}
    J -- No --> K[Manual @greptileai mention]
    K --> L[Greptile runs on request]
    L --> M[Push fourth commit]
    M --> N{Auto-run?}
    N -- Yes --> O[Greptile auto-reviews]

Loading

_{Reviews (2): Last reviewed commit: "wip: third" | Re-trigger Greptile}

[greptile-apps]

PR title does not follow the required format

The template requires <type>(<scope>)<!>: <title> DEV-1234 (e.g. docs: update README with Greptile test notes DEV-0000). The current title wip: test greptile ignore behavior omits the scope, the optional breaking-change marker, and the ticket reference. The checklist also calls for assigning yourself and tagging the PR with at least one of Front end, Back end, or workflow.

Rule Used: What: PR descriptions must follow the repository's... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

PR description missing required template sections

The template requires ### 📣 Summary, ### 📖 Description, and ### 👷 Description for instance maintainers sections (delete only if explicitly not applicable). The current description skips all three and jumps straight to ### 💭 Notes. The preview steps in the description (steps 3–7) also appear to be copied verbatim from the template placeholders rather than describing actual reproduction steps for this change.

Rule Used: What: PR descriptions must follow the repository's... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

This block — a horizontal rule plus "Hello Greptile! 👋" — is a test artifact from the experiment described in the PR and has no place in the project's README. Merging this would pollute production documentation with noise.

Suggested change

	For details about how the API documentation is implemented in each Django app,
	see [`./docs/README`](./docs/README).
	***
	Hello Greptile! :wave:
	For details about how the API documentation is implemented in each Django app,
	see [`./docs/README`](./docs/README).

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[Akuukis]

@greptileai