offu / close-issue-app Goto Github PK

Hey,
I'm unable to get the close issue app working again in my repo, it worked fine for a long period of time, but stopped working at some time.

I've justed tried to reproduce the issue in a new repo and I'm also unable to get it working there and I've also no idea how to debug this.

I suspect that it's broken in general; deleting the keywords intentionally, so see if it's broken.

In case this issue is also closed I will open a new one with the steps I've followed to set it up in my test repo.

Best,
Johannes

Is your feature request related to a problem? Please describe.

An issue transferred from another repo may not meet the requirement in this repo.
We want the bot to ignore this issue and not close it automatically.

Describe the solution you'd like

Add an option to let us control this behavior

Describe alternatives you've considered

Make exception list more configurable, eg.

...
exception:
  username1:
    allow-open: true
    allow-reopen: true
  username2:
    allow-open: false
    allow-reopen: true

Additional context
n/a

Is your feature request related to a problem? Please describe.
I installed this bot and it works fine in any new issue opened by other users, but in my case I had an old issue (that was created before I installed the bot) and I wanted to re-open the issue, however the bot was fighting against me (as an owner and admin of my own repo, it's kinda of annoying to fight against the bot). You can see what happened in this issue on my repo (I wanted to re-open the issue because the feature was not yet pushed under a new release even though I had done a commit on the issue).

Describe the solution you'd like
It would be nice if the bot could see that if the user requesting the re-opening of the issue is an owner or admin of the repo, then do nothing.

Describe alternatives you've considered
The only alternative I could think of in this case would be to uninstall the bot so that I could re-open the issue and then reinstall the bot... not ideal

Additional context
nothing else to provide

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

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency nodemon to v3
• chore(deps): lock file maintenance
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency probot to v12 [security]
• chore(deps): update akhileshns/heroku-deploy action to v3.13.15
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update codecov/codecov-action action to v4
• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• fix(deps): update dependency js-yaml to v4 (js-yaml, @types/js-yaml)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

Is your feature request related to a problem? Please describe.
With ISSUE_TEMPLATE.md where titles are defined, sometimes, users will not put enough information for a given section. e.g. if there is a title "Description" under it they will not put any content. Hence if the tool could be enhance to support regex, then one could catch that case as well.

Describe the solution you'd like
Support regex operation under the "content" setup.

Describe alternatives you've considered
One could look into rather then support regex to have support for: "between this and this title, X amount of characters must be given". It would solve the issue above but would be harder for the developer to do.

Additional context
Please ping me if that enhancement request is not clear and happy to elaborate more.

Is your feature request related to a problem? Please describe.

The keyword seems case-sensitive.

Describe the solution you'd like

make the keyword case-insensitive

Describe alternatives you've considered

No.

Additional context

Here is a issue dealt by the bot: android-hacker/VirtualXposed#308

(You can read the edit history of the issue, i just change a Character and it works.

Describe the bug
this app does not work in my repository.

To Reproduce
Steps to reproduce the behavior:

open a issue with wrong format

Expected behavior
The issue should be closed

Additional context
nothing happens

Is your feature request related to a problem? Please describe.

I'm always frustrated when I see a closed issue that I hadn't read, I click on it, and see that it's been closed by close-issue-app and not a human. A human would supply a reason I might want to know while close-issue-app keeps me sane by requiring people to complete a template. Our config looks for prompts in the template!

Describe the solution you'd like

I like that close-issue-app works and works well, but I want to label issues that were automatically closed so that I further deprioritize reviewing them.

Describe alternatives you've considered

I don't see a clear alternative. close-issue-app is responsible for the close action so it would also know to add the label.

Additional context

None.

Can anyone help me?

Describe the bug
Despite the configuration being present and working until recently, the bot no longer triggers on travis-ci/travis-ci

To Reproduce
Steps to reproduce the behavior:

1. Open a thread that does not include "Do not auto close"
2. Observe that it does not close.

Expected behavior
It should close.

Additional context
Started happening no more than 9 days ago based on automatically closed issues. Example issue that should have closed, but did not

I've reinstalled the app to try and fix it, but to no avail.

Can anyone help me?

Describe the bug
zoneminder hangs while montage tab still opened.
When I open montage - it shows everything correctly. But then you can’t switch to Console later.
I've replace local/video0 to motion daemon (connected to /dev/vide0) but have no effect. Bug still reproduced
To Reproduce
I have 6 cameras. When there were 5, no problems were observed.

1. add 6 cameras
2. open montage url
3. open console url
   Expected behavior
   console page should be opened, but montage still open.

Additional context
When I've close montage page - zoneminder restored.