Skip to content
This repository was archived by the owner on Feb 12, 2022. It is now read-only.
This repository was archived by the owner on Feb 12, 2022. It is now read-only.

Improve CLI error message "Not found." #36

@schneems

Description

@schneems

When running a CI command if there is a problem this is the only error output:

$ heroku ci:debug
 ▸    Not found.

You can get this error if the app you're running ci:debug on does not have a pipeline attached to it. Also if that pipeline is not linked to a github account.

We should explicitly account for both of those cases and give better error messages

Proposal

$ heroku ci:debug
 ▸    Error: This application `issuetriage` does not have a connected pipeline
      To add a pipeline run `$ heroku pipelines:create issuetriage`, for more 
      info see https://devcenter.heroku.com/link-to-something-explaining-why-pipelines-are-needed

and

$ heroku ci:debug
 ▸    Error: This pipeline for app `issuetriage` is not connected to a GitHub Repo
      To connect this application to a GitHub Repo and enable CI please visit
      https://dashboard.heroku.com/pipelines/374207ae-37c1-4907-bfd0-d6eef4c46a02
      And select "connect to GitHub" button.

      For more info on why this is needed please 
      info see https://devcenter.heroku.com/link-to-something-explaining-why-github-is-needed

As a side note, do we have a CLI command that allows you to connect to GitHub? That would be really nice.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions