浏览代码

AGENTS.md: sync with instructions of other repositories (#156)

A rule on `Dockerfile` version pins was mistakenly carried over into a repository without a `Dockerfile` while syncing `AGENTS.md`, so the example of rules to leave out now names that case as well. All other shared rules that fit this repository are already present.

Source: https://github.com/fphammerle/python-manchester-code/blob/5376376879d90e4965865210f878f759703982cc/AGENTS.md (proposed in fphammerle/python-manchester-code#245)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fabian Peter Hammerle 1 周之前
父节点
当前提交
7594fdc98b
共有 1 个文件被更改,包括 2 次插入 和 1 次删除
  1. 2 1
      AGENTS.md

+ 2 - 1
AGENTS.md

@@ -119,6 +119,7 @@
   a GitHub code search for `user:fphammerle filename:AGENTS.md`.
 - Creating an `AGENTS.md` for a repository: base it on **all** of them, not just one. Start from
   the closest sibling, keep only the rules that fit the particular repository (e.g. no Python /
-  `Pipfile` rules for a `Dockerfile`-only repository), and adapt repository-specific examples
+  `Pipfile` rules for a `Dockerfile`-only repository, no rules on `Dockerfile` version pins for a
+  repository without a `Dockerfile`), and adapt repository-specific examples
   (e.g. package names, commit subject conventions from `git log`). In the commit message, reference
   the individual source each part was based on with full permanent URLs (commit hash + path).