Is it conceivable add read access to the automation tab for track maintainers who are more tooling maintainers than mentors for the track, and not reaching the 100 mentoring sessions?
It makes sense to me that we don’t want write access for people who have not mentored much, to avoid poorly written feedback. However it’s still interesting to enable some access for maintainers writing the corresponding tools.
What I really want to do is add all this to a maintainers dashboard. In the interim I’m sure @ErikSchierboom could add a supermentor role into the database and check that as well as the manual check we have (roles.include?("supermentor") || ...), and then give you that role
I noticed that the version of one of the solutions I am giving feedback on–Solution #16295 Currency Exchange in Python–is different from the one I solved and also different from the current version. Would it be possible to include the problem version number? Should I create an issue for that?
We don’t actually have exercise versions. We instead use a hash of the important files in the exercise’s folder in git to determine its uniqueness.
Extrapolating your post slightly, I wonder if we should only be showing representations of solutions that pass the latest tests, which then removes the issue of giving feedback on an old solution. Does that make sense to you? (cc @ErikSchierboom for thoughts)