Auto-add to project - single repo scope

[ggnall]

Select Topic Area

Product Feedback

Body

Great to see the beta out for auto-add to project! One limitation that prevents us from using this in our projects is the ability to set rules across repos.

So I'd like to define: if [label = x,y,z] in repos 1, 2, 3 -> auto-add to project.

Since I can only scan one of several repos in the rule creation, we can't use this automation for the time being. And since it's simpler to add labels to an issue than add an issue to project(s), it would be really helpful to do so!

[2percentsilk]

Thanks for the feedback @ggnall!

How many repos are you trying to pull from for a given project? We're looking at letting you create copies of auto-add (e.g. one workflow for each repo 👀

[ThomasKasene]

This sounds promising and very much needed! Is there an issue for this in the roadmap that we can follow?
For my case at the moment, I'm looking at ~10 repositories.

[ggnall]

Currently 3, but it could increase. Cool, I would see myself adding duplicate workflows for each. It would be really cool to be able to use repos as a condition (E.g. in repos(...) AND has labels(...)).

…

We're looking at letting you create copies of auto-add (e.g. one workflow for each repo 👀 On Thu, Jan 19, 2023 at 6:16 PM, Allison Weins < ***@***.*** > wrote: Thanks for the feedback @ ggnall ( https://github.com/ggnall ) ! How many repos are you trying to pull from for a given project? We're looking at letting you create copies of auto-add (e.g. one workflow for each repo 👀 — Reply to this email directly, view it on GitHub ( #44826 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AA7KDBRHFXHP7MQSHWDARNLWTHDLPANCNFSM6AAAAAAUAY3UK4 ). You are receiving this because you were mentioned. Message ID: <community/community/repo-discussions/44826/comments/4732621 @ github. com>

[OneCyrus]

we are facing the same issue. currently we are linking about 15 repos to the same project and still increasing. would be great to have the limit much higher (100+)

[KevinEOSNation]

This is exactly what we need. The feature as-is now limits you to auto-adding 5 repos (unless you upgrade to Enterprise...but even that only gives you 20 repos)

[HazAT]

Same here, we still run our own GH Action to sync our project with multiple repos. It would be cool to get rid of this and GitHub natively adds this support for syncing multiple Repos with one Project.

[KevinEOSNation]

Hey...newbie here. How did you set that GH Action up?

[kathy-phet]

@2percentsilk - I saw that we can now "duplicate the workflow" and was temporarily excited but then disappointed ... we could work with this approach but the limit==4 is not working for us. We want to add issues from across all project repos (whole project) or across a subset of repos (e.g. 30 specific common code repos) automatically so need this limit to be much much higher. We have over 200 repos.

[rileybroughten]

👋 Hello all! Auto-add and auto-archive workflows are now available to all users, check out the announcement here as well as documentation for more details 🎉

[DFelten]

Is there a plan to remove this limitation? We work on significantly more repositories in parallel and would therefore need this workflow more often. It would be even more practical if multiple repositories could be selected in one workflow.

[Alfagun74]

the cap for free users on a single project is excessively low. i mean, nearly every project involves at least two repositories. restricting auto-add to one is distressing.

[brettcurtis]

For this to replace the GitHub action, the repo restrictions need to be removed. Teams will often prefix their repositories in a large organization. Something like myteam-my-repo and there could be several myteam-* repositories that align to a project. The dropdown for repositories needs to be replaced so we can simply add myteam-*.

Ideally, this would replace the action, not that the action is a lot of overhead really but it feels like a lot of noise in the actions all-workflow list.

[jsumners]

I've reached this issue because I want to write "in any org repo, for any issue that has title A specific title, add to project". As it is, I can only write that rule for individual repositories and the org I want this for has around 100 of them (fastify/fastify#5116).

[Rnbsov]

oh my god, i wish so much it will be implemented 😢🥺