I've got a published playground on revision N. Its state in my list is "up-to-date".
I push an update (privately) to try some behavior out. Its state in my list is now "new version" on revision N+1.
The attempt was inconclusive, so I delete that commit to get back to a clean state before I forget about it. And I push revision N back as the HEAD of the master branch. Yet the playground's status in my list remains on "new version", even though the correct commit id and description show, so published and private are the same again.
I'd have expected that status to fall back to "up-to-date". Probably some impedance mismatch from where I'm standing, since I am using git to update stuff, yet it appears the only way to reach that state is to publish.
Nothing too bad with the precious few playgrounds I've got around, but I can imagine this getting confusing down the road.
$ git push
88fca95..7c8ad2d master -> master
$ techio publish # actually I don't have a CLI I had to click :(
[hack, hack, hack]
$ git commit -am 'Try stuff'
$ git push
7c8ad2d..295fb05 master -> master
[NOPE NOPE NOPE NOPE NOPE]
$ git reset --hard HEAD^
HEAD est maintenant à 7c8ad2d
$ git push -f
+ 295fb05...7c8ad2d master -> master (forced update)