k-krawczyk opened a new pull request, #533: URL: https://github.com/apache/camel-quarkus-examples/pull/533
## Description Resolves part of [CAMEL-23823](https://issues.apache.org/jira/browse/CAMEL-23823) — *add AGENTS.md to examples repos also*. The main `apache/camel` repo already ships an `AGENTS.md`; this adds an equivalent, tailored guide to the examples repositories so AI agents know how to contribute examples here. Targeted at `camel-quarkus-main` per this repo's PR template (it tracks the current Camel Quarkus SNAPSHOT). ## What it contains A new top-level `AGENTS.md` with: - **Rules of Engagement** — the essentials carried over from the canonical [apache/camel `AGENTS.md`](https://github.com/apache/camel/blob/main/AGENTS.md): AI attribution, JIRA ticket ownership (Unassigned only, assign + In Progress), one-example-per-PR / PR volume, fork-based branches named with the JIRA id, green-CI requirement, human-approval-before-merge — plus the repo-specific rule to target `camel-quarkus-main`. - **Repo specifics** — the standalone per-example Maven module layout (no root aggregator), `quarkus-bom` + `quarkus-camel-bom` usage, JVM and native build/run, `@QuarkusTest` / `@QuarkusIntegrationTest`. - **Build / run / validate** — exact `quarkus:dev`, `package`, `-Dnative`, and `license:check formatter:validate impsort:check` commands. - **Conventions** — Maven coordinates (`camel-quarkus-examples-<name>`), `org.acme.*` packages, license headers, README structure. - **Adding a new example** — a step-by-step checklist. Content was derived by inspecting this repository's current structure, representative example modules, and CI configuration. Happy to adjust tone, depth, or any specifics to match maintainer preference. _Reported and implemented by Claude Code on behalf of Karol Krawczyk._ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
