Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: throw readable error if connecting to JIRA fails #73

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jGleitz
Copy link

@jGleitz jGleitz commented Mar 2, 2022

Description

fix #72 by throwing readable errors when connecting to JIRA fails.

This is a

  • Bug Fix
  • Feature
  • Documentation
  • Other

Checklists

Commit style

  • Changes are on a branch with a descriptive name eg. fix/missing-queue, docs/setup-guide

  • Commits start with one of feat: fix: docs: chore: or similar

  • No excessive commits, eg: there should be no fix: commits for bugs that existed only on the PR branch (see guide-to-interactive-rebasing)

Protected files

The following files should not change unless they are directly a part of your change.

  • yarn.lock (unless package.json is also modified, then only the new/updated package should be changed here)

  • package.json (renovate bot should handle all routine updates)

  • tsconfig.json (only make it stricter, making it more lenient requires more discussion)

  • tslint.json (only make it stricter, making it more lenient requires more discussion)

@jGleitz jGleitz changed the title fix: throw readable error if connecting to JIRA fails during verifyCo… fix: throw readable error if connecting to JIRA fails during Mar 2, 2022
@jGleitz jGleitz changed the title fix: throw readable error if connecting to JIRA fails during fix: throw readable error if connecting to JIRA fails Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Throws Error for Every Response Character on Connection Failure
2 participants