Skip to content

prodockit 0.36.0

Choose a tag to compare

View all tags
@buckwem buckwem released this 17 Aug 13:57
prodockit-v0.36.0
849e136
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The Surrey configure questions changed shape, from a day of running them.

Changed

  • The assessment question comes before the year, and the stage question is numbered (#437).

    The year question explains itself in terms of SRA and LSA, and nothing before it had said what those are - the question that introduces them, and lists them, came afterwards. The stage question also arrived without a number of its own, so a reader counting down met a question that was not in the count.

    5/7 Is this an assessed assignment? [Y/n]: y

    1. First
    2. SRA
    3. LSA
6/7 Which stage is it being assessed at? [1, 2 or 3]: 2

7/7 What year does the module start in? A semester 2 module should be the
    year after the Christmas break. For SRA and LSA the year should be the
    year prior to the year the retake is being assessed. [2026]:

  • Unassessed work is asked for its group and its repository name (#437), offered as <your login> and report-<your login>:

    5/7 Is this an assessed assignment? [Y/n]: n
6/7 The group or namespace the project lives under [mb0105]:
7/7 The name of the repository, and of the folder it lands in here [report-mb0105]:

    It has no cohort group to go to and no attempt to record, so a year and a stage were two questions with nothing behind them. Deriving a name from a course code is right for a cohort an examiner reads down a column of; work nobody is marking is named by whoever owns it.

  • The questions are worded as they were asked for (#420). The login question had lost the example that made it answerable - a student logs in with ab1234@surrey.ac.uk, so "the six-character ID" asks about something they may never have typed alone. The year question had lost the rule for a resit and gained a different one.

Fixed

  • A first run printed the stage list over the details it had just told you to note down (#433). The namespace and the repository name are the only two values a reader carries from this command to a browser, and twenty-three stage lines printed after them scrolled both away. It stops there now, where --configure already did.

  • The ssh-agent step ended the run without looking (#435). 0.34.0 stopped that step looping and overshot: the moment you said the service was started, the run ended and asked you to start again. A started service usually is visible to the next command that looks - ssh-add opens the agent's pipe afresh each time - so the check is given its chance, and a run that can carry on carries on. The message no longer suggests opening a new window, which never did anything running the command again would not.

Full notes in the changelog.

Assets 2
Loading