How to manage and update Slicer dependency forks?

It is convenient to have staging area to maintain and test patches that are being contributed back to official repositories.

The following wiki page outlines the naming convention for branches pushed to such fork:

Also, by default when visiting most of these projects on GitHub you will now see the content of a welcome branch and its associated including answers to questions like:

  • What is this project ?
  • What is the branch naming convention ?
  • How to update the version of NameOfProject ?

We hope that this will enable more developer to contribute and help reduce the bus factor.

For example, see:


Very nice. Thanks for setting this up @jcfr!