fix: return non-zero if there were errors in processing

[renaissanceGeek]

Fixes #80 very simply. There may be something more elegant, but at least this helped my use case!

[pattacini]

I like the simple logic @renaissanceGeek 👍🏻
I'm just wondering if you're willing to deal also with the error conditions caught inside add_repo_collaborator that now won't make the job exit 1.

You may turn has_errors into a global var (e.g., $has_errors) as $org to handle those 3 further conditions.

Instead, a better way would be to make add_repo_collaborator return false when one of those 3 exceptions occurs so that you'll be able to account for that with has_errors locally to the main.

Just a note for myself

Since the automation may take quite some time to complete, it is convenient not to stop it early in presence of errors/warnings – which usually are not blocking – so that the specific errors can be accounted for even manually soon afterward.

Differently from this logic, the script check-automated-repositories shall exit as soon as an exception gets found as it is done right now so that the PR check can provide immediate feedback.

[renaissanceGeek]

OK, I think I resolved your requests. I tried testing various error conditions that could come up in add_repo_collaborator and successfully failed :-)

[pattacini]

Fantastic job @renaissanceGeek 🚀
I've only added a missing return true and dealt with just another call to the function.

Thanks again for your contribution!
Appreciated.