Most contributors to openjdk/jdk will want to take advantage of automated testing, and most reviewers will expect that as well. But there are no instructions for doing so. Here are my personal notes:
I visited https://github.com/Martin-Buchholz/jdk/actions and it said
Workflows aren't being run on this forked repository
Because this repository contained workflow files when it was
forked, we have disabled them from running on this fork. Make sure
you understand the configured workflows and their expected usage
before enabling Actions on this repository.
They're now enabled. Do the skara docs need to clarify this?
The same happened with jdk16. If you want automated testing, then after
creating the personal fork, visit e.g.
https://github.com/Martin-Buchholz/jdk16/actions - you will see "Workflows
aren't being run on this forked repository". Then click on the big green button
to enable them.
I visited https://github.com/Martin-Buchholz/jdk/actions and it said
Workflows aren't being run on this forked repository
Because this repository contained workflow files when it was
forked, we have disabled them from running on this fork. Make sure
you understand the configured workflows and their expected usage
before enabling Actions on this repository.
They're now enabled. Do the skara docs need to clarify this?
The same happened with jdk16. If you want automated testing, then after
creating the personal fork, visit e.g.
https://github.com/Martin-Buchholz/jdk16/actions - you will see "Workflows
aren't being run on this forked repository". Then click on the big green button
to enable them.