[FEATURE]: Update bot in-develop labeler to accept more kinds of closing statements
- Dominant language
- CSS
- Stars
- 11.8k
- Forks
- 2.4k
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 4
Description
>Users could use multiple close statements. The complete list can be seen [**here**](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
To make the process easier, I thought of making an array including all the keywords, then checking if the PR contains one of those keywords.
_Originally posted by @Panquesito7 in https://github.com/devicons/devicon/pull/1410#discussion_r1045307225_
In addition to this, we might be able to [get linked issues and/or pull requests from the GitHub API](https://stackoverflow.com/a/60780499/12206312):

Contributor guide
Research direction
Start by locating the bot's in-develop labeler and reviewing the linked GitHub documentation for the complete closing-keyword list. Determine whether the change should check those statements directly or use linked issues and pull requests from the GitHub API; done means every supported closing statement is recognized and the labeler behaves correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100