Prepare hack.commit.push

Things we need to do before hack.commit.push:

• short video introduction of the project
• link to a guide on how to create JUnit 5 extensions
• make sure the good first issue and up for grabs labels are properly applied

Things we could do:

• rename master to main ~> #331
• update dependency on JUnit to prevent problems if updating becomes necessary during the event
• add existing extension ideas (e.g. from JUnit 5’s issues) as issues

[nipafx]

HCP is over now, so we’ve obviously done everything. 😊

[nipafx]

Regarding the JUnit 5 version we depend on:

We usually want to depend on the lowest minor version (newest patch of that) that supports our feature set. Generally speaking, that’s still the case, but the upcoming hack.commit.push event required an exception. Updating from Jupiter 5.6 to 5.7 requires some changes to our test code, which means it’s a bit disruptive. In case some contributors need to update during the event, they would also need to make these changes in our test code, which would be an unnecessary burden. To preempt that, I decided to update to 5.7 now.