Skip to content

Conversation

@khvn26
Copy link
Member

@khvn26 khvn26 commented Dec 31, 2025

Thanks for submitting a PR! Please check the boxes below:

  • I have added information to docs/ if required so people know about the feature!
  • I have filled in the "Changes" section below?
  • I have filled in the "How did you test this code" section below?
  • I have used a Conventional Commit title for this Pull Request

Changes

In this PR, we attempt to revamp our developer documentation, and make it accessible for human contributors and LLM-based agents alike.

  • Add AGENTS.md
  • Add missing developer documentation
  • Refresh CONTRIBUTING.md
  • Refresh the PR template
  • Import developer docs and CONTRIBUTING.md to docs.flagsmith.com

How did you test this code?

Mainly, observed with make -C docs serve.
TODO: report on AGENTS.md performance.

- Add missing developer documentation
- Refresh CONTRIBUTING.md
- Refresh the PR template
- Import developer docs and CONTRIBUTING.md to docs.flagsmith.com
@khvn26 khvn26 requested review from a team as code owners December 31, 2025 07:05
@khvn26 khvn26 requested review from Holmus and Zaimwa9 and removed request for a team December 31, 2025 07:05
@cursor
Copy link

cursor bot commented Dec 31, 2025

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.

@vercel
Copy link

vercel bot commented Dec 31, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Review Updated (UTC)
docs Ignored Ignored Preview Dec 31, 2025 11:45am
flagsmith-frontend-preview Ignored Ignored Preview Dec 31, 2025 11:45am
flagsmith-frontend-staging Ignored Ignored Preview Dec 31, 2025 11:45am

@github-actions github-actions bot added front-end Issue related to the React Front End Dashboard api Issue related to the REST API docs Documentation updates and removed docs Documentation updates labels Dec 31, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 31, 2025

Docker builds report

Image Build Status Security report
ghcr.io/flagsmith/flagsmith-e2e:pr-6448 Finished ✅ Skipped
ghcr.io/flagsmith/flagsmith-api-test:pr-6448 Finished ✅ Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-6448 Finished ✅ Skipped
ghcr.io/flagsmith/flagsmith-api-test:pr-6448 Finished ✅ Skipped
ghcr.io/flagsmith/flagsmith-frontend:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith-frontend:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith-api:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith-private-cloud:pr-6448 Finished ✅ Results
ghcr.io/flagsmith/flagsmith-private-cloud:pr-6448 Finished ✅ Results

@codecov
Copy link

codecov bot commented Dec 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.06%. Comparing base (2d208b1) to head (5feac3c).
⚠️ Report is 14 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@khvn26 khvn26 requested a review from Copilot December 31, 2025 07:10
@github-actions github-actions bot added docs Documentation updates and removed docs Documentation updates labels Dec 31, 2025
@khvn26 khvn26 changed the title docs: Add developer documentations, AGENTS.md docs: Add developer documentation, AGENTS.md Dec 31, 2025
Copy link
Contributor

Copilot AI left a 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.

khvn26 and others added 3 commits December 31, 2025 11:30
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
@github-actions github-actions bot added docs Documentation updates and removed docs Documentation updates labels Dec 31, 2025
@github-actions github-actions bot added docs Documentation updates and removed docs Documentation updates labels Dec 31, 2025
Copy link
Member Author

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.

Copy link
Contributor

@matthewelwell matthewelwell left a 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?)

@github-actions github-actions bot added docs Documentation updates and removed docs Documentation updates labels Dec 31, 2025
Copy link
Contributor

@Zaimwa9 Zaimwa9 left a 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
Copy link
Contributor

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.md and api/claude.md for 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

Copy link
Contributor

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 ?

Copy link
Member Author

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.
Copy link
Contributor

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 😄 )

Copy link
Member Author

@khvn26 khvn26 Dec 31, 2025

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.
Copy link
Contributor

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

Copy link
Contributor

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

Copy link
Member Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api Issue related to the REST API docs Documentation updates front-end Issue related to the React Front End Dashboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants