Jamie Nelson

@jmisur can you use `pull_request_target` instead of `pull_request`?

You can also use this fork, which handles the looking up the KEYS from the Pull request commits, the jira title, the string, etc. And also can create a CHANGELOG...

My fork does it: https://github.com/Broadshield/gajira-find-issue-key

As in: ```yaml name: Pull Request - Jira Integration on: pull_request: types: - synchronize - create - edit jobs: jira_integration: runs-on: Ubuntu-18.04 env: JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL...

> @jamie-wearsafe are you planning to open a PR to add this feature to this action? I'm not since my fork has had so many additional features added to it....

> @jamie-wearsafe > > tried your action and getting following error: > > > **Error: TypeError: github.GitHub is not a constructor** Hi, Yes this is due to a change in...

> > > @jamie-wearsafe > > > > tried your action and getting following error: > > > > > > > **Error: TypeError: github.GitHub is not a constructor** >...

@Justin-JHG sorry for the delay, its done. Please test if that solves it for you. https://github.com/Broadshield/gajira-find-issue-key