Project auto-add workflow shows "no repositories found"

[zsloane]

Select Topic Area

Question

Select Feature Area

• Issues
• Projects

Body

I am trying to setup the "Auto-add to project" workflow and all I see is this:

Does anyone know if I need to turn some setting on somewhere to make this work? My organization has plenty of repos that I have access to so it's not actually that none exist.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[anderskiaer]

We see the same, even after we have linked existing repositories to the project by:

1. Going to https://github.com/<organization>/<repository>/projects
2. Clicking Link to project and then selecting the relevant project.

[mnpenner]

This was working on Apr 26 but now no repositories are listed. Not in the Repository column, nor the "Add item from repository" button.

[marywhite]

Hi @zsloane! Can you provide more information about your situation? Is this only happening on a single project? Is the project a personal project, or one that belongs to your organisation?

[zsloane]

Hi @marywhite

This is for all projects within my organization. I suspect the answer to this is that the feature hasn't been released in "enterprise cloud" since it looks like it's going into the yet to be released GHES 3.9

Not sure why it shows up at all in the UI then. It would be nice if someone from GitHub could reply

[zsloane]

Can anyone from GitHub chime in here??

I still cannot use this workflow. All I see is the message that we have no repositories which is definitely not accurate.

I was hoping this was somehow tied to GHES 3.9 (even though we are not using GHES, we are on some sort of Enterprise account...) but it seems like that is not the case now that it has been released.

[anderskiaer]

We still face this issue. Debugging it a bit, it looks like the API call used by the GItHub frontend does not return private repositories.

E.g. the API call going to https://github.com/orgs/<organization>/projects/beta/suggestions/repositories in the background when selecting the "Auto-add to workflow" returns {"repositories":[]} if all repositories are private. If we change to/create public repositories, those repositories are listed in the response and selectable by the "Auto-add to workflow".

[zsloane]

I suspected it was something like this.

However, since this feature is not in beta and there is no mention of it not supporting private/internal repos in the docs, this clearly seems like a bug.

I really wish someone from GitHub would provide some clarity here.

[Amnesthesia]

We're having this issue as well

[hotyes]

same here

[joelveloso]

same here

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[zsloane]

I still would like to know if this is a bug or is working as intended. There is no documentation for this that suggests private repos are not supported

[keikoro]

I'm running into the same problem with (public) repositories which don't have issues enabled.

Which may not always be immediately obvious. Forks, for example, seem to have issues disabled by default. Which, granted, makes sense in general, but is something users could be warned about – e.g. on the repo's project page if not on the workflow page itself.

[keikoro]

Interestingly, in the above scenario, once issues are enabled and the workflow subsequently (allowed to be) set active, issues can be disabled again and the workflow remains active...

[zsloane]

This appears to be working now for me. I do not know as of when, but I no longer get the "No repositories found" message