-
Notifications
You must be signed in to change notification settings - Fork 466
docs: Add developer documentation, AGENTS.md #6448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Add missing developer documentation - Refresh CONTRIBUTING.md - Refresh the PR template - Import developer docs and CONTRIBUTING.md to docs.flagsmith.com
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on January 10. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Docker builds report
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6448 +/- ##
=======================================
Coverage 98.06% 98.06%
=======================================
Files 1292 1292
Lines 46509 46509
=======================================
Hits 45611 45611
Misses 898 898 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see a guide similar to api/README.md here — calling @Flagsmith/flagsmith-front-end for help.
matthewelwell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this! Thanks @khvn26 .
Added a few fairly minor comments.
We'll want to get feedback from @talissoncosta and @Zaimwa9 and update frontend/README.md sooner rather than later (perhaps even as part of this PR?)
Co-authored-by: Matthew Elwell <[email protected]>
Zaimwa9
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A first few comments before reading the details
| @@ -0,0 +1 @@ | |||
| Read @AGENTS.md No newline at end of file | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 comments:
- I don't know if file references works the same as when in CLI
- My understanding leads me to think that having subdirectory claude.md would give us the result we want
frontend/claude.mdandapi/claude.mdfor respective guidelines
Claude Code reads memories recursively: starting in the cwd, Claude Code recurses up to (but not including) the root directory / and reads any CLAUDE.md or CLAUDE.local.md files it finds. This is especially convenient when working in large repositories where you run Claude Code in foo/bar/, and have memories in both foo/CLAUDE.md and foo/bar/CLAUDE.md.
https://code.claude.com/docs/en/memory#how-claude-looks-up-memories
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm reading everything and its opposite about the @ referencing/importing so don't trust my word. Did you have any confirmation it works ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you have any confirmation in works ?
Just got Claude to generate #6451 on top of it. I did observe it correctly calling the makefile targets for backend. No idea if that confirms anything, though.
I don't know if file references works the same as when in CLI
My guess is @-style saves a bit of tokens, but I'd be happier for those to be normal markdown links, actually. It seems that AGENTS.md examples do use markdown links, so I'm leaning towards changing them.
| - `mappers.py` for data mapping logic unrelated to API requests and responses. | ||
| - `services.py` for encapsulated business logic. Our goal with this layer is to make the views, models and serialisers leaner, so that the business logic is more clearly defined and easier to compose. | ||
| - `tasks.py` for defining asynchronous and recurring tasks. | ||
| - `types.py` for custom type definitions, including typed dicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this part we could add a couple of rules too. I'm actually thinking about the "imports at the top of the file" which is often ignored and other with naming for example (i'm not thinking about much more on the top of my mind 😄 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm consciously avoiding adding guidelines that can, and should, be linter rules. Import placement/order is definitely one of those. As for naming conventions, I'd love for us to have them eventually; examples are very welcome.
This section is very deliberately incomplete, and I encourage any suggestions to expand it!
| @@ -0,0 +1,10 @@ | |||
| Prioritise @AGENTS.local.md, if present. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me agents is working with chatgpt/codex. So we could also add the cursorrules to cover most of them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could we have those rules in any LLM_RULES or self-explanatory name and symlink the claude.md, agents and cursorrules to it ? or as you did with agents actually, but given we are more using Claude, i would use Claude.md as the source
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Cursor docs, AGENTS.md is considered an alternative to cursorrules. Does this imply that simply having AGENTS.md is enough?
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
In this PR, we attempt to revamp our developer documentation, and make it accessible for human contributors and LLM-based agents alike.
How did you test this code?
Mainly, observed with
make -C docs serve.TODO: report on
AGENTS.mdperformance.