Connect GitHub to Flots: issues and pull requests

Follow GitHub issues and pull requests inside your Flots projects.

Updated

The GitHub integration brings your issues and reviews into Flots. A repository linked to a project turns its issues into tasks there, which the whole team can follow without opening GitHub. It's included in the Pro and Team plans.

Connect your GitHub account

  1. Open Settings › GitHub and click Connect GitHub.
  2. GitHub opens and offers to install the Flots app. Pick the accounts and repositories Flots can reach.
  3. Come back to Flots: the connection updates on its own and shows GitHub is connected.

To add or remove a repository later, use Manage accounts and repositories. From the mobile app, the connection goes through your phone's browser, then brings you back to Flots.

Issues and reviews land in Flots, filed in the right project.

That link is what turns issues into tasks.

  1. In Settings › GitHub, in the Repositories and projects block, pick the project each repository feeds.
  2. Or, from the project: open its settings, under Linked GitHub repositories.

A repository feeds one project only. In that repository, the issues assigned to you or opened by you, and the pull requests you're asked to review, become tasks of the project. The task takes the title, links back to GitHub, and a checklist written in the issue comes across as sub-tasks.

Keep up with your issues and reviews

In your planner, the GitHub block has two tabs, Issues and Pull requests: what's assigned to you, the reviews you've been asked for, and CI status. Click a pull request to list its checks, failures first.

When an issue is closed or a pull request merged, the task shows up under Finished on GitHub. Complete closes it, Finish all closes them all. Flots doesn't do it for you: a merge doesn't always mean the planned work is done.

Choose what notifies you

For each repository linked to a project, you pick the notifications: New issue, Issue resolved, New pull request, CI failed. These settings live in Settings › GitHub and in the project's settings, kept in sync. Only the person who connected GitHub receives them.

What the rest of the team sees

Development tasks are project tasks like any other. The project manager or the sales lead see their status and sub-tasks alongside the rest of the work, with no GitHub account.

For a whole team, the Set up Flots for a startup path shows where GitHub fits.

Disconnect GitHub

In Settings › GitHub, Disconnect cuts off access. Tasks already created stay. The app stays installed on the GitHub side: to remove it completely, go through Manage accounts and repositories.

Frequently asked questions

Do the other project members need a GitHub account?

No. Only the person who connects GitHub needs one. Everyone else follows the development tasks like any other task in the project.

Does closing an issue complete the task in Flots?

Not on its own. The task shows up under Finished on GitHub, with a Complete button: you're the one who confirms.

Does Flots change anything in my repositories?

Flots can edit an issue's labels, with your rights on the repository. It doesn't close issues or touch their content.

Your question isn't here?

A message or a video demo: someone from the team replies within 24 hours.

Where do you want to start?

One account, everywhere, in sync. 2 months free, no credit card.