Feature Request: Consolidated Code Push

[bcfletcher]

For our FLL teams, we use 6-10 tasks (separate) python files all controlled via a menu.py file.
To push all our tasks, robot library, robot config.py, and individual task .py files we have to switch to the menu.py and hit |> button.
the kids (and adults) frequently forget and press |> for the active tab. this results in only that tab being sent to robot and usually results in bad consequence.

we would like a way to make the menu.py the "main" file so when in other tab if we hit |> it actually send the menu.py and all its dependencies to the robot.

[dlech]

There is already #1903 for this feature request.

[bcfletcher]

thanks. We prefer implementation 1 or 2 as the approach for designating a master file.

I expand on this a bit further in #2175 by expanding the concepts further by tying it to hub_menu()

Really the only two complaints I get from my FLL kids are

1. how to save multiple tasks to the hub and reference them on the hub menu
2. the saving issue discussed above.

so defining a way to define the master or root file and integrating that with a hub_menu would really improve ease of use for FLL and similar robot competitions

[dlech]

I would suggest to put this comment on #1903 so that the feedback doesn't get lost. GitHub doesn't make automatic links to issues mentioned from discussions.