You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing around with this feature on my fork, and I wonder if it would make sense to skip the archived repos by default given only an org as an input.
Hi @mtfoley!! Good question: I think for now, yes, skipping archives within an org is probably fine (especially since they won't be getting any real updates. Maybe in the future we'll want to index those unless there's some sort of weird naming clash we can't handle. i.e., a archive has the same name as a new repo)
Type of feature
🍕 Feature
Current behavior
Right now, if someone wants to source all their repos within a single git repository, they'd need to do it one by one.
Suggested solution
It'd be great if there was the ability to iterate all repos in a github org and source them all at once.
The
/bake
route can stay the same, but we could add a member to the posted data that denotes a github org. Maybe something like:Open to other suggestions on how this could be tackled as well!
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: