This action runs on the issue.closed event and scans the repository for any issues that need to be finished/closed before closing the issue.

You: Work with a team to write code for some software product and your team uses Github Issues for managing the development process.

You: Have dozens, perhaps hundreds of issues in your backlog, and you're having a hard time managing that.

For example: How do you know, when going through your tickets that it's a bad idea to close #217 because blockers #175 & #173 aren't finished yet?

That is where autoissuebot enters the picture!

Add it to your repositorys' actions, then, when you close issue #217, it will scan the body of all open issues in the repository for the text "blocks #217"

Then if those matching issues are found it will reopen #217 and add a comment that says:

"This issue cannot be closed at this time, it is dependent on issue #175, #173"

REQUIRED Github Repository Token.

NOT Required Configure the # of issues per page when making requests to github

  Default: 30
  Max: 100

List of issues this issue is dependent on

blockers: "#175, #173"

uses: autoissue/autoissuebot@v1
with:
  repo-token: 'repository token'

uses: autoissue/autoissuebot@v1
with:
  repo-token: 'repository token'
  per_page: 50