This will help us in so many ways, thank you for working on this!
Are you going to add stubs for issues in the bugtracker? (just the subject line, a link to the issue tracker, maybe first N lines of the issue description)
A few tweaks (none of them very important):
-Maybe we could fix links to the SVN repository (e.g., the commit comment contains “git-svn-id: http://svn.slicer.org/Slicer4/trunk@28773” but this URL is not valid)
Maybe add a url to the corresponding commit in the old repository (so that we can easily find a commit based on the old hash)
Andras can confirm my co-authorship for the two commits which I think it was lost in the review/merge process. If it is not possible to add the co-authorship anymore, no problem.
Thanks!
Thank you @jcfr for performing this migration with so much attention to all details. Preserving all the various links, history, contributions, etc. will be very valuable.
Can we start submitting pull requests (and rebase&merge them)?
“Allow force pushes” and “Allow deletions” unchecked: This make things safer and simpler (at the cost of not being able to cover up potential missteps). It also allows us to use commit count as a monotonously increasing counter for easier revision tracking (instead of SVN revision). It is a minor inconvenience that merge count does not appear in github GUI, but we can determine it quite easily at project build time.
Require pull request reviews before merging: checked (we should try this at least and disable if we find it too annoying or it slows things down too much)
Require status checks to pass before merging: unchecked (for now, until we are confident that checks work very reliably)
Require signed commits: unchecked (I have never used this, but probably not necessary)
Require linear history: checked (non-linear history is just too complicated)
Include administrators: unchecked (there is a warning displayed anyway if you exercise this right, that should be enough)
Restrict who can push to matching branches: checked (have a CoreDevelopers or similar sub category who are allowed to merge changes)
Disable “Create a merge commit” option (only allow “Squash and merge” and “Rebase and merge”). Merge commits make reviewing change history a very complicated task.
Create Developers group and add people who we want to be able to assign issues to.