I want to use Micro:bits with my students.
It is a grade 10 class, so I do not want to use block language but JavaScript for the beginning students.
For more advance students I want them to use MicroPython in CodeSpace IDE.
They all use GitHub Classroom to get their repo.
For students using MicroPython I have created a template Repo that I can push to them using GitHub Classroom.
(https://github.com/TEJ2O-Templates/TEJ2O-Template)
It loads uFlash (https://pypi.org/project/uflash/).
They then use py2hex, it creates the *.hex file, they download it locally (to their Chromebook) drag the file over and it flashes.
They can push their changes back to the repo as normal.
Everything works great.
They get to use python, Codespace and a modern IDE.
For the students that are starting out, I have added the Micro:bit MakeCode files into the same repo.
(1 repo for all students and if they finish the JavaScript way, they can transistion over to using Codespace)
They go to MakeCode Micro:bit and use the “add URL” command.
Update their code and flash it.
All works great.
The problem is that MakeCode Micro:bit will not let the students “push” changes to their code back to the GitHub repo that GitHub Classroom gave them. If they fork the repo it works, but I do not want them doing that. The problem seems to be since my Org is the owner of the repo, even though they have permission to change it, MakeCode Micro:bit will not let them.
Any suggestions?
Thanks, Patrick