Summary

MicroPython has a code-size workflow but no automated way to track how PRs affect memory footprint over time or compare against previous commits.

This PR adds MemBrowse CI integration for automated memory footprint analysis on pull requests.
It creates a PR comment with the size changes on region and section level with links to the full build comparison page.

It was discussed with@AJMansfield on Discord, who suggested opening a PR.
Here is an example of the dashboard and its features:https://membrowse.com/public/membrowse/micropython

This includes:

• membrowse-targets.json - contains the configuration of the targets to be analyzed
• membrowse-pr.yml — runs on PRs + pushes to master, builds firmware and uploads reports to MemBrowse
• membrowse-comment.yml — posts consolidated memory results as PR comments (runs after membrowse-pr.yml)
• membrowse-onboard.yml — one-off workflow for building the last N commits (N is an input to the workflow) to have historical data on day one
• README badge linking to the MemBrowse MicroPython dashboard
• Currently the integration supports 8 targets. Same ones used by the code-size workflow.

Setup for maintainers:

• Create account athttps://membrowse.com
• Create a project and link it to this repo
• Set the project as publicly available.
• Add MEMBROWSE_API_KEY as a GitHub action secret

Run the onboard workflow to populate the dashboard with historical data.

Testing

End-to-end validation performed on a personal fork

Trade-offs and Alternatives

External dependency.

Maintenance

As the author of MemBrowse, I'm committed to maintaining this integration and ensuring it continues to work correctly.
If issues arise, feel free to ping me on Micropython's discord or or atmichael@membrowse.com.
Happy to adjust boards, scope, naming, or workflow triggers based on feedback.