Point all past runs to archive branches

[encukou]

No description provided.

[encukou]

The archive branches have the archive/ prefix, so we don't touch them by mistake.
I've set up GitHub branch protection so that only owners/maintainers can push to them.

[hroncok]

Do we want this? I mean, people delete branches, apparently, but I was fine having all branches at my own forks.

[encukou]

There was a Slack discussion on this recently.
I think we do want this for most other forks.
I think the branch namespace is a good idea: people tend to make branches for quick PRs under pyvec; it should be clear which ones can be deleted.
As to your fork, will this inconvenience you? If not, might as well do the same thing everywhere -- it might help with automating this later.

See #419 for the 2017/2018 archival.

[hroncok]

As to your fork, will this inconvenience you?

Not really, I don't change the past branches at all.

[encukou]

So, is it good to go?

[hroncok]

The idea? Yes. But I haven't checked if the branches match the previous content nor whether the change is conplete. Do you want me to?

[encukou]

No, unless you want to :)
I'll check the output and merge if it's similar enough.

[encukou]

The diff was too much for meld at one point, but it looks OK:

• "Canonical" courses have code highlighting differences due to newer pygments. I'd say they're improvements – e.g. async is a keyword; print is not.
• 2018/czechitas-ostrava-jaro has the same differences (see Archive the 2018/czechitas-ostrava-jaro run #578)
• iCal formatting changed somewhat with the new version of ics, but AFAICS the information is the same.
• Edit URLs changed to the archives, of course