Flare Error tracking made for Laravel
Features Pricing Docs Blog Log in Start free trial Free trial
  • Docs
  • Videos

Documentation

  • General

    • Welcome
    • Projects
    • Errors
    • Error occurrences
    • Using the API
    • Sharing error occurrences
    • Spike protection
    • GitHub integration
  • Ignition for Laravel

    • Installation
    • Configuration
    • Security
    • Controlling collected data
    • Sending logs to Flare
    • Linking to errors
    • Identifying users
    • Adding custom context
    • Adding glows
    • Writing custom middleware
  • Flare for generic PHP projects

    • Installation
    • Controlling collected data
    • Identifying users
    • Linking to errors
    • Adding custom context
    • Adding glows
    • Writing custom middleware
  • Javascript error tracking

    • Installation
    • Framework integrations
    • Resolving Bundled Code
    • Reporting errors
    • Client hooks
    • Adding custom context
    • Adding glows
    • Solution Providers
  • Solutions

    • Introduction
    • Adding custom solutions
    • Making solutions runnable
    • Using solution providers
    • Writing good solutions
  • Notifications

    • Configuring notifications
    • Mail
    • Slack
    • Telegram
    • SMS
    • Webhooks
    • Discord
    • Microsoft Teams
  • Team management

    • Using multiple teams
    • Subscribing to a plan
    • Receiving invoices
    • Managing team members
    • Inviting guests to projects

GitHub integration

If you use GitHub to track issues in your app, you can connect Flare to GitHub.

Our 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

Go to the GitHub page within the team settings and click on the connect with GitHub button.

screenshot

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.

screenshot

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.

screenshot

By pressing this button you can quickly create an issue in GitHub.

screenshot

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.

screenshot

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.

screenshot

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.

screenshot

Previous topic Next topic

On this page

  • Getting started
  • Associating Flare errors with GitHub issues / PRs
  • Resolving Flare errors and closing GitHub issues / PRs

About Flare

  • Home
  • Features
  • Pricing
  • Support

Resources

  • Blog
  • Changelog
  • Docs
  • Ignition

App

  • Log in
  • Start free trial
SPATIE
  • Service status
  • Terms of use
  • Privacy & cookie policy