# Collaborator unable to link package to repository

**URL:** <https://forum.gitea.com/t/collaborator-unable-to-link-package-to-repository/11110>\
**Category:** Gitea Usages\
**Created:** [April 10, 2025, 5:41am UTC](https://forum.gitea.com/t/collaborator-unable-to-link-package-to-repository/11110 "2025-04-10T05:41:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MAW](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/maw/32/6239_2.png) [@MAW](https://forum.gitea.com/u/MAW)\
**Post date:** [April 10, 2025, 5:41am UTC](https://forum.gitea.com/t/collaborator-unable-to-link-package-to-repository/11110/1 "2025-04-10T05:41:12Z")

</div>

I have a `jenkins` user that is a collaborator on my Gitea repositories for CI/CD purposes, generally with Write permissions on each one. I’ve just started dabbling in publishing docker packages to Gitea, so I might be misunderstanding what the workflow is supposed to be.

I’m able to push a package to the `jenkins` account from my Jenkins build process, but when I go to the package’s settings to link it to a repository, there are no repositories in the dropdown at all. The `jenkins` account isn’t the owner of any of these repos, but even with Administrator permissions set under Collaborators for the one I’m interested in, no repos are available to choose from.

Packages are enabled on the repo in question. Am I missing some other setting?

---

<div class="post-metadata">

**Author:** ![MAW](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/maw/32/6239_2.png) [@MAW](https://forum.gitea.com/u/MAW)\
**Post date:** [May 5, 2025, 7:57pm UTC](https://forum.gitea.com/t/collaborator-unable-to-link-package-to-repository/11110/2 "2025-05-05T19:57:09Z")

</div>

Update: I believe this is caused by the fact that the repo is private, per [Package Registry related ToDo list · Issue #19270 · go-gitea/gitea · GitHub](https://github.com/go-gitea/gitea/issues/19270#issuecomment-1086911000)