docs: clarify contributor and agent workflows - #525
Conversation
E2E — mocked backend🎭 E2E Tests✅ All green — 350 passed · 0 failed · 1 skipped, across 28 spec files in 8m 50s. By spec file
All 351 tests — click to expand
Slowest 10 — what the shard counts should be tuned against
📼 Download the HTML report, videos and traces — see the Generated by run 34434183266 from |
E2E — real Fineract🎭 E2E Tests✅ All green — 77 passed · 0 failed · 0 skipped, across 23 spec files in 6m 49s. By spec file
All 77 tests — click to expand
Slowest 10 — what the shard counts should be tuned against
📼 Download the HTML report, videos and traces — see the Generated by run 34434183266 from |
|
I will hold this one see #477 we can also add optional disclosure in PRs and also a policy that contributor is responsible for the AI generated code. |
Understood. I’ll leave #525 in your hands while the discussion in #477 moves forward. I’ll focus on other projects for now, but I’m happy to revisit this if there’s a clear follow-up. |
|
@zhangxinyao88 You can do similar to apache/fineract#6366 (comment) here |
|
And also you can add dedicated AI disclosure like what tools they used harness etc . (Optional not mandatory) |
Thanks, I’ve added the Backoffice version to this PR: the policy, optional tool/harness fields in the template, and a disclosure for this PR. |
Summary
AGENTS.mdAI assistance (optional)
Validation
npm run format:checkgit diff --check