Skip to main content

Fix a project's push warning

When you open a project whose repository is on GitHub, Jaah checks whether your own Git connections can push to it. When none can, a warning shows above the project's tabs. Fixing it there saves a task from finishing work it can't deliver.

A task pushes with the Git account of the person who started it, so this warning is about your access. It can say something different to a teammate. A project whose repository Jaah manages shows no warning.

Who can do this: anyone who can open the project sees the warning about their own access.

Read the warningโ€‹

  1. In the sidebar, select Directory, then the Projects tab, and select the project's name.

  2. Read the line above the tabs:

    WarningWhat it means
    Tasks can't push here.None of your Git connections can push to this repository or open a pull request there. The rest of the line says what is missing, such as the Jaah GitHub App not being installed on the repository's owner, or a connection with read-only access. Tasks you start would do their work but couldn't deliver it.
    Tasks push as a connection name**: your selected GitHub connection can't write here.**Nothing to fix. Your tasks push with the connection it names, in place of the one you selected.

Fix itโ€‹

  1. Select Fix at the end of the line, when it shows. It opens the right GitHub page in a new tab, such as the page to install Jaah's app or to add the repository to the app's access.
  2. Make the change on GitHub that the line asks for. Without Fix, do what the line says yourself, for example ask a repository admin to give your account write access, or connect a token that has it on your profile's Git section.
  3. Go back to the project and reload the page. The warning can take a few minutes to clear after a fix.
  4. Check that the line is gone. A line that names a different problem means one step is still missing: repeat from step 3.