I would cheat by creating a new empty repo, git pushing the same git repository contents into it, and then swapping the repo names (and eventually deleting the original repository).

This of course isn’t a great strategy if one has forks/stars, in which case I’d contact:

https://support.github.com

Thanks for your reply! I’ve thought about that before, but I have around 300 stars and I don’t want to lose them, so this would probably not work for me. Thanks though.

Thanks for the detailed description of the problem you’re facing.
Could you please try adjusting your workflow so that it runs on all pushes to your main branch, e.g.

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

That should ensure that any PR against main will have a baseline of alerts to compare against, and resolve the error about the missing analysis. It’s possible that some existing commits on main don’t have corresponding analysis results (either because of the path filters or the period of time in which you turned off the analysis), so this suggestion should fix the problem for future commits and PRs. If the problem persists, please let us know here and we’ll be happy to investigate further.

Hmmm, I just tried that but it still shows a neutral check. For example, test by evanyiwensu · Pull Request #54 · HACKERALERT/Picocrypt · GitHub. I’m not sure what the culprit is, but thanks for helping me make some progress :slight_smile:

Thank you for the clear and concise response! I will just leave it as is since it seems like there’s a lot to do to get rid of the notices. Thanks for your help.

Hello
Int (" hello-meni":);