Inspired by TesseractCoding/Issue_Watcher

Attributions for original action: @anushkrishnav @ricardoprins

Modded & tailored by @Suvraneel =>

Changelog :

• Triggers on /assign not on creation of Issue & PRs
• acts on assignees[] and not on author
• Unassign assignee & remove labels instead of closing issues
• Works best when combined with JasonEtco/slash-assign-action

Rogue Spammers with a mission to disrupt the peace of the valley ? Fear not we will STOMP the Spammers

New Update : adding 'on-review' tag on an issue will stop it from being closed by the Bot allowing contributors to create more than the limited count

This tool was created to helps you to protect your project from being spammed.
You can customize the maxIssue to set the maximum count of active issue a contributor can have.
The project is currently a work in progress, so it might have bugs. If you do find bugs, please report it here

Example workflow

name: check

on:
  issues:
    types: [opened]

jobs:
  first-job:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout code
        uses: actions/checkout@main
    - name: Action
        uses: TesseractCoding/Issue_Watcher@main
        with:
          token: ${{ secrets.GITHUB_TOKEN }} # default token in GitHub Workflow
          author: '${{github.actor}}'
          repo: {owner}/{repo} # your repo
          maxIssue: {any integer} #default is set as 2

Contributing Guidelines

• Plagiarism is strictly not allowed. Any work that is found to be suspicious of plagiarized work will not be merged.
• Issues will be assigned on a first come, first serve basis. You just have to comment on the issue, asking to be assigned, and it will be done if found fit.
• Preferably, you cannot work on any issue that is not assigned to you.
• In case you want to submit an improvement , we prefer that you create an issue, describing in details your improvement. This will help others to analyze your contribution. You can use the templates that we have provided :)
• If you have anything else in mind, create an issue and please wait for it to be assigned to you. You can then start working on it and create a PR.
• All PRs must be made from a Branch. Create a separate branch for every Issue you are working upon and once found fit, make a PR.
• If you have no idea what are issues or PRs, please do refer to this link

Make sure your code works before submitting it and always write test for every new function that you create or improve :D

Code Styling and Linting

We use pre-commit framework to maintain the code linting and python code styling. We encourage our contributors to follow the industry followed pattern, while contributing to the code. we would like to maintain the code thorough Linters and stylers for better quality and readability.

The pre-commit configuration file is present in the repository contains the different code styling and linting guide which we use for the application.

Just run pre-commit before Commiting your changes. Following command can be used to run the pre-commit:
$ pre-commit run --all-files

If pre-commit is not installed in your system, it can be install with :
$ pip install pre-commit

Our Contributors

CONTRIBUTORS.md

Code of Conduct

You can find our Code of Conduct here.

Note

This project is a WIP. If you find a security threat or bug please feel free to open up an issue and we will get to it shortly

Created by Anush Krishna

Uses

PyGithub - Awesome package that made this action possible

actions/container-action - Container Action Template

jacobtomlinson/python-container-actionTemplate - amazing starter template

License

MIT licensed. See the bundled LICENSE file for more details.