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
Today, there are bot errors/issues that arise – which are typically permission issues - example would be the GitHub app not being installed. This may have happened bc at the time of the commit, GitHub app was not installed, and Codecov still had uploads running. Said differently, Codecov wasn't able to use the GitHub app to post the data. To summarize:
the GitHub app install requirement could be shown more broadly (currently on the org page and commit leve)
if the installation is made, the error is out of date in it's tense
initial issue / context
Move bot errors to a be more repo scoped, as that are not exactly commit level.
Current we show bot errors, or errors with the GitHub app on the commit page only, mean that do not clear when the issue is fixed. This messaging should be more of a real time status at the repo level.
Problem to solve
Today, there are bot errors/issues that arise – which are typically permission issues - example would be the GitHub app not being installed. This may have happened bc at the time of the commit, GitHub app was not installed, and Codecov still had uploads running. Said differently, Codecov wasn't able to use the GitHub app to post the data. To summarize:
initial issue / context
Move bot errors to a be more repo scoped, as that are not exactly commit level.Current we show bot errors, or errors with the GitHub app on the commit page only, mean that do not clear when the issue is fixed. This messaging should be more of a real time status at the repo level.
Slack Message
Solution
The text was updated successfully, but these errors were encountered: