Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: ability to fetch all repos in a GitHub org #32

Open
2 tasks done
jpmcb opened this issue Aug 8, 2023 · 2 comments · May be fixed by #41
Open
2 tasks done

Feature: ability to fetch all repos in a GitHub org #32

jpmcb opened this issue Aug 8, 2023 · 2 comments · May be fixed by #41

Comments

@jpmcb
Copy link
Member

jpmcb commented Aug 8, 2023

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:

curl -d '{"org":"https://github.com/open-sauced"}' \
  -H "Content-Type: application/json" \
  -X POST http://localhost:8080/bake

Open to other suggestions on how this could be tackled as well!

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs
@mtfoley
Copy link

mtfoley commented Aug 31, 2023

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.

@jpmcb
Copy link
Member Author

jpmcb commented Aug 31, 2023

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)

@mtfoley mtfoley linked a pull request Sep 1, 2023 that will close this issue
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants