Project Naming Conventions in GITHUB

We are migrating from perforce to GITHUB , we have a deeply nested structure in perforce and we cant follow the same in GITHUB.

Example

ProductName-ServiceName-Version-Public/Private-ArtifactName
example webs-subscription-v3-pub-signup.
Can we move this as is to GITHUB.

We also have a requirement where the same service can have multiple versions and each version is a totally different implementation and cannot have the same master repository.
Is introducing version numbers in the project naming conventions a good practice for the above mentioned use case.