tachiyomiorg / issue-moderator-action Goto Github PK

I was updating my files today, January 10, 2024. However, I was shocked that the updates from yesterday were continued within the same date. Previously, whenever I update library entries on the next day, a new date appears on top of the updates.

The command would be /ext or something else. It would close the issue and leave a comment about reporting to the extension repo instead. Maybe apply invalid label as well.

This will help to notice issues that were closed by mistake. Related issue - #342

My attempt to do this for existing sources - https://github.com/scb261/issue-moderator-action/compare/main..existing-show-url
But it didn't work - scb261#5

Investigate https://github.com/tachiyomiorg/tachiyomi-extensions/issues/15918

What should be added?

Add alias to the existing commands that are more bot-like.

When some user uses it, the comment would be marked as resolved or hidden.

The command would be /cf or /cloudflare and would do the same as the cloudflare regex in the extension repo.

Right now, the auto-close feature will only close issues that match the regex. I think it'd be useful to be also able to auto-close if the regex isn't matched through a flag. This way the auto-close could be used to enforce templates being used.

My proposal would be a boolean option like closeifMatch which defaults to true which is the current behavior. By setting to false the regex must match to avoid closure.

 [
    {
      "type": "title",
      "regex": ".*Placeholder title.*",
      "message": "@${issue.user.login} this issue was automatically closed because it did not follow the issue template",
      "closeifMatch": true
    }
  ]

What should be added?

A command that allows the user to edit the current issue title by a specified new one.

Can be used by Edit title to <new-title> or /edit-title <new-title>.

Expected behavior

• User creates a new source request issue in https://github.com/tachiyomiorg/tachiyomi-extensions/, including the URL
• Action checks if new issue is a source request
• If yes, then check repo index.min.json for duplicate URL.
  • If duplicate found, close issue and abort action
  • If no duplicate found, continue
• If no, continue

Sometimes issue body contains old URL in its body, and the issue is closed as a duplicate. Most often it's because source name contains old URL in its name, and sometimes user mentions old URL in other details.

Should take substring of the body after Source new URL and before Other details.

Examples of issues with this problem:

• https://github.com/tachiyomiorg/tachiyomi-extensions/issues/16893
• https://github.com/tachiyomiorg/tachiyomi-extensions/issues/16802
• https://github.com/tachiyomiorg/tachiyomi-extensions/issues/16359
• https://github.com/tachiyomiorg/tachiyomi-extensions/issues/16475

Note: consider that the check also applies to new source requests that don't have Source new URL section.

Currently the extension repo uses duplicate check for both Domain changed and Source request, but the comment for duplicates always explains that the source was already requested. Possible ways to generalize the comment:

• Remove explanation about already existing source and only keep Duplicate of #dddd.
• Change explanation to explain both Source request and Domain changed cases.
• Rewrite code to allow customizable comment for different labels. Need to also consider cases when original and duplicate issues have different labels.

I'll open a PR with the first solution. Opening the issue to consider/discuss other possible solutions.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update dependency vitest to v2.0.3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

the rule that regexp needs to be matched.
I want to prevent deleting all template text.

Could consider having tests that create issues and assert their states/comments.

Could use https://github.com/octokit/action.js/