If a label was previously applied to a repository, the GitHub API returns a 422 Unprocessable Entity error. However, this error could also mean that invalid fields were sent, see the API documentation.
Distinguishing these two cases requires additional API calls, which we want to avoid.
The user currently has the option to output a tibble with details about the repositories and labels that were (un)successfully created, if requested. However, by default, the peer_init() function currently does not inform the user whether or not labels were successfully created.
Note that issues will still be created even if labels were not applied to a particular repository , therefore fixing this has a lower priority.
If a label was previously applied to a repository, the GitHub API returns a
422 Unprocessable Entityerror. However, this error could also mean that invalid fields were sent, see the API documentation.Distinguishing these two cases requires additional API calls, which we want to avoid.
The user currently has the option to output a tibble with details about the repositories and labels that were (un)successfully created, if requested. However, by default, the
peer_init()function currently does not inform the user whether or not labels were successfully created.Note that issues will still be created even if labels were not applied to a particular repository , therefore fixing this has a lower priority.