We're proud to share that errors on Flare can now be associated with issues on GitHub and vice versa. This integration allows to:
-
create a GitHub issue directly on a Flare error
-
associate a GitHub issue with a Flare error by mentioning a Flare URL in the GitHub issue
-
automatically resolve an error on Flare when you close the GitHub issue
-
automatically close a GitHub issue when you resolve an error in Flare
Getting started
In team settings you'll find a new page titled "GitHub". On that page you can click the connect with GitHub button.
Flare will ask read and write access to your issues and pull requests on your GitHub account.
After you've connected Flare to GitHub, you can connect Flare projects with GitHub repositories. In the project settings, there's a GitHub page. On this page, you can select a repository that should be connected with the project.
Associating Flare errors with GitHub issues / PRs
After you've connected a GitHub repo to a Flare project, you'll see an extra button "Create issue" on each error in Flare.
By pressing this button you can quickly create an issue in GitHub.
Alternatively, you could manually open an issue at GitHub and mention add a Flare error URL in the issue description or any of the comments. This will also associate the GitHub issue with the Flare error.
When you return to Flare, you can see that the UI now shows that this error is now associated with one GitHub issue.
When you click that link, you'll see a card that contains a link to the issue, and you can optionally couple the same error to another issue.
You can link a GitHub issue or pull request with an error by adding the URL to the Flare error in the title, body or comments of the issue or pull request.
Resolving Flare errors and closing GitHub issues / PRs
Flare will automatically resolve an error when an issue was closed, or a pull request was merged.
Optionally, you can let Flare close GitHub issues whenever an error is resolved. You can opt-in for this behaviour by checking the last option at the GitHub screen in the team settings.
In closing
We think GitHub integration is a handy feature for a lot of our users. Internally we've built our integration VCS agnostic. If we get enough feedback from our users that Gitlab or Bitbucket integration is wanted, we'll consider supporting those too.
You can see other improvements we recently made on our changelog. Do you have an idea to improve Flare? Let us know!
Continue reading
Lessons from the deep end
20 months ago, we started building Performance Monitoring as Flare’s next big feature, never expecting Laravel’s rapid commercial growth to put us in direct competition with their own tools. This is our honest take on those 20 months went, how we’re adapting to this new reality, and where we’re heading next while staying true to who we are. A dive into the deep end, without knowing how far down it goes.
Alex
Connect your AI agent to Flare to automatically fix production and performance problems in PHP and Laravel projects
You can now use our MCP server to connect your AI agent to Flare. This way your AI has all context it needs to diagnose and fix production and performance problems.
Freek
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates