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

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

  • The API and Pagure Web UI uses the singular fork, for example https://pagure.io/fork/csomh/copr/copr or https://pagure.io/api/0/fork/csomh/copr/copr

  • Git URLs to clone the repositories and the fullname fields of the API use the plural forks, for example ssh://git@pagure.io/forks/csomh/copr/copr.git or "fullname": "forks/csomh/copr/copr".

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?


Metadata