New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't assume running in git directory #174
Comments
I stumbled upon this today when running tests (and hence coverage and There is also this section:
which runs |
This is preventing us from having coveralls write a status to the triggering PR commit hash when building against the PR with the tip of the target branch merged in. The id value is being set to the tip of the merged branches and it doesn't look like there is a way to override that setting. |
Hey folks, Sorry for the lack of response on this -- the I would be happy to accept a PR for either or both of those changes (ie. "only attach git data when the |
I'm gonna give a try at PRing silently omitting the git request json key. Expect it in an hour or two tops. |
This issue has been fixed by @nirizr and I will post back here once I cut a new release. Keeping this issue open as a reminder to myself to de-dupe the |
@nirizr @wwaltersp @giorgiosironi I have just released version 1.3.0, which includes @nirizr 's fix for this issue. Sorry this took so long! |
I've just hit this when working with a Mercurial repo. Should be running the most recent version of coveralls which should be able to work without git. Obviously not.
|
Addresses this comment: TheKevJames#174 (comment) Previously, git info was omitted if git was installed but the .git directory was missing. This fix will also omit git info in case git itself is missing (unless, of course, the environment args are there).
@Themanwithoutaplan PR linked above should solve this issue, which is caused by the git command being unavailable (which wasn't handled previously). |
I'm running a version that should contain the merged PR – it contains my own for using Mercurial instead of Git. Will try and doublecheck in docker and see if I can remove the dependency. |
Addresses this comment: TheKevJames#174 (comment) Previously, git info was omitted if git was installed but the .git directory was missing. This fix will also omit git info in case git itself is missing (unless, of course, the environment args are there).
Addresses this comment: #174 (comment) Previously, git info was omitted if git was installed but the .git directory was missing. This fix will also omit git info in case git itself is missing (unless, of course, the environment args are there).
Right now coveralls assumes it runs inside a git directory while executing the following two lines:
However they are not really mandatory. First, the only use of
rev
is as kind of a last resort default value, which is often calculated without being used (as more often than not, environment variables supersede it).The other variable,
remotes
is used but does not seem to be crucial to the operation of coveralls.I would greatly appreciate if coveralls could function outside of git directories either by not providing the
remotes
parameter or by manually providing it using an environment variable or command line argument.The text was updated successfully, but these errors were encountered: