Add Ability To Send Attachments To Separate Channels

This PR allows users to specify "sub-channels" for their team's release notes to go to.

View channels in the "configuration" docs, for more info.

Explicitly Ignore Issues in PR Body

#37 adds the ability to stop Captain's Log from picking up issues tied to a pull request. This could be valuable for people who are mentioning related tasks, subtasks, etc..

Issues Closed

#36

Update Empty State To Include Org/Repo

#34 forgot to include empty state, this release adds that.

Update Default Heading

#34 is the only PR in this release, and it closed both #32 and #33.

Summary

• Changed default heading to include the org and repo that initiated captain's log
• Removed hard-coded Jira value from empty state message

Introduce Github V4 API (GraphQL)

As part of the resolution for #16, we introduced the v4 github api to retrieve tags. This fixes an issue for all users where if they had naming conventions other than that of semver, for their releases, their tag filters would not find any matching tags therefore their release logs would not show any changes.

Fix Team Messaging With Multiple Issue Trackers

Fixed: #29

Remove Support For Leading Number In Jira Regex

Minor bug that took odd inputs and reported them as valid Jira tickets in Captain's Log.

Jira supports A-Z as a default for the first character in a Jira Project, thus we will support that as well.

Whitespace Formatting Fixes

We restricted the limits on line wrap and truncation. See #21 for more info.

Ticket Finders (i.e. Github Issue Support )

Ticket Finders

This release we're introducing Ticket Finders. These will allow for a much easier integration path with <insert ticketing system here>.

Github Issues

This change also enables priority support for github issues.

• Teams support, meaning you can have multiple github projects under a single team. (Any non-team projects will show up in the General bucket)
• Linked issues to github or github enterprise will be reported in Captain's Log
• github close syntax is supported

Formatting Changes

• We have bumped up the truncation of the title from 34 characters to a default of 70. (When adding messages, we specifically set the truncate to 60 to allow for Pull Request Numbers to be linked as well)
• With that comes line wrapping. We've added some logic to support for Stories and/or Details wrapping, allowing the other to correctly insert new lines when needed.

Fix Jira Regex

We were not supporting team names like JIRA2-1234 which is perfectly valid. This will allow teams to use any valid Jira name for their tickets.