Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #710 +/- ##
=======================================
Coverage 97.04% 97.04%
=======================================
Files 50 50
Lines 2335 2335
=======================================
Hits 2266 2266
Misses 69 69 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
db577b5 to
ad18fa4
Compare
eva-1729
left a comment
eva-1729
left a comment
There was a problem hiding this comment.
I asked some advice from Copilot on this (it seemed relevant as it is an agent) and it suggested having a specific "must follow" area, vs. general guidance. Is that possible to consider with this?
|
The way I see it the whole thing is general guidance and anything that is a MUST, has the word must in as part of the overall guidance. i.e. general unless otherwise stated. |
|
Okay that makes sense to me; this one covers quite a lot so it would be hard to break things out into a specific section that applies to all of it anyway |
|
Another thought: there doesn't seem to be any mention of perhaps a line where, at some point, the agent would need to hand over to a person. It might be good to outline this sort of boundary. |
|
So in some parts I do say when to hand back to a person, for example with regards to information that is not trivially accessible. i.e. issue number for the pull request. Where do you think we should add more? |
…t-lsp FIA-API now fronts `POST /script/analyse` for the script editors, which makes mantid-python-script-lsp a downstream dependency with a wire contract that lives in two repositories at once. Record it where an agent changing either side will meet it: the pass-through rule, why the byte-based size cap has to be agreed between the two services, and why a cache hit has to carry the caller's own `content_hash` rather than the one stored.
…stion The instruction described the label as something to attach, and named two label spellings to look for, which reads like a judgement call left for whoever opens the PR. Name the label, the command, and the moment it happens.
Part of https://github.com/fiaisis/planning/issues/43
Description
Add
AGENTS.mddocumentingfia-api's position within the overall FIA service architecture (overarching pipeline map and upstream/downstream/sibling repository contracts), directory-level repository structure,pyproject.tomland environment conventions, testing/linting requirements, issue and PR workflows, and Dependabot handling.