How can I prevent Satis from erroring when a repostiory has no `composer.json` present?

[JacobDB]

How can I prevent Satis from erroring when a repostiory has no `composer.json` present?

[SvenRtbg]

Sounds like you should be scanning for the composer.json file and skip the repo if it is missing. Not having this file means it is unusable for Composer anyways.

[JacobDB]

Thanks, that's one solution I did consider, I was just hoping to avoid making a ton of API calls every time a build is created. I was hoping there was a way to pass a flag to Satis to ignore invalid repositories.

[alcohol]

Had a quick peek at https://docs.gitlab.com/ee/api/groups.html#list-a-groups-projects

My suggestion would be to add a satis topic to the repositories that are considered valid / ready-for-use and simply use that as a selector in your API request.

Although that works on a project level, and it has been ages since I used Gitlab, so I am not sure if a project equals a repository or not.