AGENTS.md: document the enforced commit conventions

[0x1 (EmbeddedAndroid)]

Going back over the last year of reviews, I noticed several conventions that the maintainers enforce which are not written down in our new Agents.md. Add them alongside the existing commit-message guidance:

• the Signed-off-by identity must match the author and be a real, routable address rather than a GitHub web-editor noreply
• subjects use a lowercase component prefix rather than Conventional Commits or kernel-tree prefixes
• branches are rebased on master rather than merged
• and added patch files carry an Upstream-Status header.

I'm happy to adjust if some of these rules seem too strict.

Writing these down keeps commits consistent and is the groundwork for enforcing the deterministic subset automatically in the very short future.

[Dmitry Baryshkov (lumag)]

As you are writing the docs, would you also mind a human-targeted set of recommendations to author the commits?
Main points:

• Each commit should contain an atomic set of changes, "Foo also bar and, as we are at it, baz" is a bad idea
• Each commit message should start by describing the problem or the issue that is being solved.
• Other useful tips and requirements (valid SoB chain, git cherry-pick -x for backport commits, use of -s if one picksor aplies commit authored by somebody else, etc.).

[0x1 (EmbeddedAndroid)]

As you are writing the docs, would you also mind a human-targeted set of recommendations to author the commits? Main points:

• Each commit should contain an atomic set of changes, "Foo also bar and, as we are at it, baz" is a bad idea
• Each commit message should start by describing the problem or the issue that is being solved.
• Other useful tips and requirements (valid SoB chain, git cherry-pick -x for backport commits, use of -s if one picksor aplies commit authored by somebody else, etc.).

Good idea, added as 2b91af9

[Ricardo Salveti (ricardosalveti)]

Here we should include all the valid patterns, and it is missing Inactive-Upstream.

[Ricardo Salveti (ricardosalveti)]

As you are writing the docs, would you also mind a human-targeted set of recommendations to author the commits? Main points:

• Each commit should contain an atomic set of changes, "Foo also bar and, as we are at it, baz" is a bad idea
• Each commit message should start by describing the problem or the issue that is being solved.
• Other useful tips and requirements (valid SoB chain, git cherry-pick -x for backport commits, use of -s if one picksor aplies commit authored by somebody else, etc.).

Good idea, added as 2b91af9

I would prefer if we could keep this part outside AGENTS.md, as this is for humans and it contains a bit of duplication, which would just burn tokens.

We could extend https://github.com/qualcomm-linux/meta-qcom/blob/master/README.md#contributing or just add a new entry at https://github.com/qualcomm-linux/meta-qcom/tree/master/docs.

[Dmitry Baryshkov (lumag)]

I think a separate document is the best idea.

[Dmitry Baryshkov (lumag)]

Granted the lack of updates for 3 weeks I've proposed #2652

[Koen Kooi (koenkooi)]

Granted the lack of updates for 3 weeks I've proposed #2652

Since that one has been merged, can this PR be closed?