#5017 inconsistency: fork vs. forks
Opened 3 years ago by csomh. Modified 3 years ago

There is a small inconsistency in how namespaces for forks are called:

This inconsistency can lead to surprises when writing automation that works both with the Pagure API and clone and work with Git repositories: when trying to use forks/csomh/copr as a unit of namespace, API calls fail. fork/csomh/copr works, but cloning will fail with a URL constructed from this unit. (My usecase is: configure the namespace on which a script should work on, and construct API calls and URL for git operations from that.)

Should this inconsistency be fixed? In which way?


Log in to comment on this ticket.

Metadata