fork: fix clonning for projects within subgroups

Projects placed within a subgroup in gitlab was not being cloned while using 'fork' cmd. Even though the project was being properly forked in gitlab, the issue was that only the first path part (after namespace) was being used as the project name to be clone from user's namespace, e.g. 'user/group/project' was being handled by lab as a project with name 'group' instead of 'project'. This patch uses the last path part always, regardless the project being placed within a group or not. Signed-off-by: Bruno Meneguele <[email protected]>
zaquestion · Sep 9, 2020 · d4dfe5e · d4dfe5e
1 parent f8306df
commit d4dfe5e
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/cmd/fork.go b/cmd/fork.go
@@ -70,7 +70,11 @@ func forkToUpstream(cmd *cobra.Command, args []string) {
 		log.Fatal(err)
 	}
 	if !skipClone {
-		cloneCmd.Run(nil, []string{strings.Split(args[0], "/")[1]})
+		projectParts := strings.Split(args[0], "/")
+		// In case many subgroups are used, the project's name forked will be
+		// the last index
+		projectName := projectParts[len(projectParts)-1]
+		cloneCmd.Run(nil, []string{projectName})
 	}
 }
 func determineForkRemote(project string) string {