search

ls1intum / Artemis

Artemis - Interactive Learning with Automated Feedback
https://docs.artemis.cit.tum.de
MIT License
483 stars 288 forks source link

Allow cloning and pushing (without CI) in the time-span between Release Date and Start Date #9209

Open dfuchss opened 1 month ago

dfuchss commented 1 month ago

Is your feature request related to a problem?

No response

Describe the solution you'd like

Currently, our tasks involves two phases:

  1. At the release date the students get the task; CI & Repositories are disabled (Start Date Feature in Artemis)
  2. One week late, the start date occurs: The Artemis repositories are activated

We'd like to enable the Repositories directly at Phase 1. Nevertheless, the tests & CI should not be triggered for commits within the first phase. Thus, the students can already use the Repository but have to think about the problem on their own (without the tests). Since, we now have LocalVC this should be rather easy to handle.

Describe alternatives you've considered

No response

Additional context

No response

Strohgelaender commented 1 month ago

Should there be an automatic build of the current repository state once the start date is reached?

dfuchss commented 1 month ago

Could be, but for us it would be enough if the CI is activated once start date is reached.

dfuchss commented 1 week ago

After talking to @krusche :

Idea: Between Start and Release Date of the task, we can allow clone and disallow push with a message that pushing is allowed at the beginning of the start date. That should be part of the advanced settings of Programming Tasks