The constraint on `:name` here effectively negates the use of the `*name` glob parameter. Should the `name` be able to contain '/' or not? My (admittedly brief) investigations show that a '/' in a repo name will be converted to '-', so it would appear not. If '/' is not allowed you should be using `:name` rather than `*name` since the latter implies acceptance of multi-segment values.

You should also probably wrap these routes in a `constraints` block so that the `name` constraint is consistent across all of them.