question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add a (hidden) flag to skip squash/rebase merge PR check.

See original GitHub issue

I have a customer reporting that they can consistently produce this error using the --ci flag on version 5.6.2 of the CLI:

✖ Failed to retrieve git information
HTTPClient Failed to fetch https://api.github.com/repositories/<id>/pulls?base=nre-storybook&direction=desc&per_page=10&sort=updated&state=closed, got 502/Bad Gateway

If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at support@chromatic.com if chat is not an option.

Please provide us with the above CLI output and the following info:
{
  "timestamp": "2021-04-30T18:11:43.175Z",
  "sessionId": "5f1765f9-5e1c-46d0-800c-2d00bf8a9c9e",
  "gitVersion": "2.20.1",
  "nodePlatform": "linux",
  "nodeVersion": "14.16.1",
  "packageName": "chromatic",
  "packageVersion": "5.6.2",
  "flags": {
    "interactive": true,
    "projectToken": "************",
    "ignoreLastBuildOnBranch": "nre-storybook",
    "preserveMissing": true,
    "exitOnceUploaded": ""
  },
  "buildScript": "./.storybook/build-storybook.sh",
  "errorType": "GraphQLError",
  "errorMessage": "✖ Failed to retrieve git information"
}

See https://app.intercom.com/a/apps/zj7sn9j1/inbox/inbox/all/conversations/27253920694 for full GitHub url.

Upon asking them to upgrade to 5.8.0, they said that the issue happens intermittently & that the --ci flag has no effect on the outcome.

It looks like an issue with the GitHub API, but the fact that it is consistent is odd. Any ideas on what could be going on?

┆Issue is synchronized with this Asana task by Unito

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:18 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
tmeasdaycommented, May 17, 2021

Haven’t heard back from GH yet @nigel-codaio

1reaction
tmeasdaycommented, May 7, 2021

I’m guessing you’ll also have problem with the PRs screen inside Chromatic! GH are working on the problem at their end.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Pull request "Squash and merge" button changes author details
It was merged using the GitHub UI "Squash and merge" button (so that it would be rebased onto the current tip of origin/master)...
Read more >
Squash and merge - GitLab Docs
Go to the merge request and select Edit. · Select or clear the Squash commits when merge request is accepted checkbox. · Select...
Read more >
Squash commits considered harmful - DEV Community ‍ ‍
I used to insist devs squashed/rebased/etc. their commits before opening a PR and then use rebase-merge to merge the PR into main. Over...
Read more >
root [<branch>] git rebase --continue | --skip | --abort
<upstream> are omitted (i.e., a patch already accepted upstream with a different commit message or timestamp will be skipped). It is possible that...
Read more >
When do you use Git rebase instead of Git merge?
But if you merge using the --squash option, all of the commits made on branch B will be "lumped together" and merged as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found