GitHub children’s shoes are familiar with Issues. It is an important way to connect maintainers and consumers.

For maintainers:

  1. Can collect and deal with bugs and new features of the product.
  2. Build product-centric communities.
  3. According to the issue, the weak link and future trend of the product can be located.

For users:

  1. You can use issue consultation, or query past issues to solve your own problems.
  2. Exchange experiences with different users, and maybe international friends.
  3. Communicate with maintainers and participate in product development.

Therefore, there are often hundreds of Issues to be dealt with in each major project, and the number is increasing every day. For a long time, maintainers have brought a very big problem: so many Issues, how to effectively automate management?

Next, let me introduce today’s protagonist:

Issues assistantGitHub Action to automatically manage Issues

What is GitHub Action?

GitHub Actions is officially provided by GitHub to automate, customize, and execute software development workflows in the repository. You can discover, create and share operations to perform whatever work you need (including CI/CD), and combine operations in a fully customized workflow.

Based on this, the Issues-Helper uses GitHub Actions to help you handle issues.

Who is using it?

  • ant-design
  • ant-design-vue
  • umi
  • dumi
  • vue-request

âœĻ features

  • 😎 completely free
  • 🚀 Full automatic operation
  • 🏖 is hosted on The GitHub server and is not affected as long as GitHub does not go down

ðŸĪš Quick start

1. New Action

Click Actions for the warehouse. If Actions have been added, the following screen will be displayed.

Click New Workflow to add.

You can click On Set Up a Workflow Yourself to create a custom action, or you can use the template to create an action. Template usage.

2. Write the Action

Actions to store address is fixed, unified as /. Making/workflows/xx. Yml.

Take the example of the home page below to elaborate. The corresponding scenario is as follows: When the help wanted tag is added to an issue, the system will automatically comment on it.

name: Issue Reply
on:
  issues:
    types: [labeled]
jobs:
  reply-helper:
    runs-on: ubuntu-latest
    steps:
      - name: help wanted
        if: github.event.label.name = = 'help wanted'
        uses: Actions - cool/[email protected]
        with:
          actions: 'create-comment'
          token: The ${{ secrets.GITHUB_TOKEN }}
          issue-number: The ${{ github.event.issue.number }}
          body: | Hello @ ${{lot. Event. Issue. User. The login}}. We totally like your proposal/feedback, welcome PR. Hello @ ${{lot. Event. Issue. User. The login}}, we completely agree with your proposal/feedback, welcome to PR.Copy the code

View detailed parameters.

3. Enable the Action

When you’re finished writing and committed to the main branch, the workflow is automatically enabled, triggering conditions as defined by on.

🌈 Function List

The functionality that has been added so far basically covers most common issue usage scenarios. Detailed usage and parameters can be found in the online tutorial.

⭐ based

  • add-assignees
  • add-labels
  • close-issue
  • create-comment
  • create-issue
  • delete-commen
  • lock-issue
  • mark-duplicate
  • open-issue
  • remove-assignees
  • remove-labels
  • set-labels
  • unlock-issue
  • update-comment
  • update-issue
  • welcome

⭐ advanced

  • check-inactive
  • check-issue
  • close-issues
  • find-comments
  • lock-issues

conclusion

Welcome to try, at the same time in the process of using the problem, welcome to feedback through the following way ~

  • Use Issue to report bugs or consult
  • Discussions are conducted through Discussions
  • submitPull RequestTo improve theissues-helperThe code of

Finally, happy New Year to you all 🎉