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
Currently, if one isn't use one of the supported CI providers, there is no way to associate results with a PR. It would be nice if the API allowed me to pass this information to coveralls, if I have access to it.
Ideally, I'd like to specify the commit, the branch it will be merged to, and whether the build is against the result of merging, since we do builds before creating a PR, rather than after. This seems like it should be enough information to report commit status (#25).
The text was updated successfully, but these errors were encountered:
Also, it would be nice not to need to know the pull request. We often (usually?) build and test things before opening a PR, so that information isn't available when we submit it.
Sorry I'm not sure what you mean by not needing to know the PR -- if it wasn't yet associated with one it would build on another branch per usual. Could you clarify?
Currently, if one isn't use one of the supported CI providers, there is no way to associate results with a PR. It would be nice if the API allowed me to pass this information to coveralls, if I have access to it.
Ideally, I'd like to specify the commit, the branch it will be merged to, and whether the build is against the result of merging, since we do builds before creating a PR, rather than after. This seems like it should be enough information to report commit status (#25).
The text was updated successfully, but these errors were encountered: