replyowl 0.2.2__tar.gz → 0.3.0__tar.gz

{replyowl-0.2.2 → replyowl-0.3.0}/.gitignore

@@ -4,11 +4,15 @@ __pycache__/
 *.py[cod]
 
 # uv and packaging
-.venv/
+.venv*/
 /build/
 /dist/
 uv.lock
 
+# mise
+mise.local.toml
+.mise.local.toml
+
 # Development tools
 .cache/
 .coverage*

replyowl-0.3.0/AGENTS.md

@@ -0,0 +1,30 @@
+# Environment/Tools
+
+* `mise` manages dev tools and tasks, including `uv` which manages Python and dependencies.
+* Use `uv add`/`uv run python` instead of bare `pip`/`python`
+* `mise install`: After-clone setup (install tools, dependencies, pre-commit hooks)
+* `mise run lint`: Pre-commit hooks (via `pre-commit`-compatible `prek`) including lint, format, type check (ruff, ty)
+* `mise run test`: Run tests (accepts pytest arguments)
+* `mise run lt`: Lint+test (no arguments)
+* `mise run snapup`: Update test snapshots (syrupy, accepts pytest arguments)
+
+# Commit conventions
+
+* Keep commit messages concise and in plain language, so a maintainer can
+  quickly understand the change. Use a short subject, and add a body only when
+  the change needs explaining, in a few lines about why. Don't list changed
+  files, restate the diff, or report test results.
+* If a commit contains code or text largely generated by an LLM, add an
+  `Assisted-by: <tool>:<model>` trailer, for example with `git commit --trailer`.
+* Don't add `Co-authored-by` or `Signed-off-by` lines for LLM tools, links to
+  LLM sessions, or promotional lines such as "Generated with [...]".
+
+# Submitting contributions
+
+* You may commit locally without asking. Before submitting anything, such as
+  pushing commits or creating or editing a pull request, issue, or comment,
+  show the user (who is the contributor) exactly what will be submitted, and
+  wait for their explicit approval. Submit it as approved. This includes but is
+  not limited to commit messages, titles, and bodies.
+* Keep titles and descriptions short and specific. Don't restate what the diff
+  already shows.

replyowl-0.3.0/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing to replyowl
+
+**Contributions are welcome!**
+
+Thank you for your time and interest in improving
+**replyowl**!
+
+## Project resources
+
+* **Web site**: **<https://smkent.github.io/replyowl>**
+  for general project information, usage, and development documentation
+* **Repository**: <https://github.com/smkent/replyowl>
+  for submitting pull requests
+* **Issue tracker**: <https://github.com/smkent/replyowl/issues>
+  for questions or bug reports
+
+## Contribution terms
+
+By submitting a contribution to replyowl, you agree that it is
+licensed under the project's license, the
+[GNU Lesser General Public License v3.0 or later](https://github.com/smkent/replyowl/blob/main/COPYING.LESSER),
+with no additional terms,
+and that you have the right to submit it under that license.
+
+## LLM use
+
+A contributor is always the author of their contributions.
+You must read, review, and understand everything you submit, including
+LLM-generated code or text, and be able to explain it on request.
+
+If a commit contains code or text largely generated by an LLM, add an
+`Assisted-by: <tool>:<model>` trailer to its message. This can be done
+automatically with `git commit --trailer="Assisted-by: <tool>:<model>"`.
+
+Do not use `Co-authored-by:` for LLM attribution. LLMs are tools, not authors.