These are the results for the performance tests:

Generated by 🚫 dangerJS against 6863d15

I think that this change defeats the purpose of the introduction of the playground. The problem I tried to solve was:

1. I need to test a change in isolation
2. I open docs/pages/x/introduction/index.js
3. I copy & paste the reproduction on the GitHub issue
4. I make a fix
5. I start to make a commit
6. 💥 pain. I need to git reset the changes done in docs/pages/x/introduction/index.js

We are introducing pain 6 back with this PR:

I think that the trap is that gitignore only applies to files that are not tracked yet. This PR tracks docs/pages/playground/example.tsx so gitignore has no impact anymore.

An improved version proposal: mui/material-ui#34739

@oliviertassinari The original implementation had the same "issue" you are referring to—if you were to modify playground.example.tsx—the changes appear in git.
The idea is that developers would create their own playgrounds in playground folder and example.tsx just serves as that—an example.

I was initially unaware of this workflow to test components in isolation and changes were made to adapt to the way others (Siriwat, Flavian) got used to using it.

By no means—I do agree that this process could be improved and it's discoverability made better (like what you are suggesting in your PR 👍 ).

The original implementation had the same "issue" you are referring to—if you were to modify playground.example.tsx—the changes appear in git.

@LukasTy Ah right makes sense 👍, I misinterpreted how this new file was supposed to be used. The changes looks good then.

So mui/material-ui#34739 is only about pushing the solution a step forward with, e.g. documentation on how to use it.

My current usage is as followed:

I have one playground which is cleaned several times a day (pages/playground.tsx right now, could be pages/playground/temp.tsx for instance).
On this one I do basically what @oliviertassinari describes.
I copy paste reproduction cases, doc examples etc... anything I want to play with right now.

But I also have other playgrounds (currently new-pickers.tsx) which I can keep for weeks and that I don't want to loose between two sessions of work on a given PR.

I never touch pages/playground/examples.tsx.