Closed Ash258 closed 2 years ago
This repository breaks the GitHub community guidelines of misinformation and disinformation. You are effectively mystifying scoop users that they can use my personal and shovel-org buckets, which is not true in most cases. And it could negatively influence their usage of scoop and I do not want to be connected with them. Like I do not care that your users will be confused about it, but you as a scoop developers, should be worried about this state.
Effectively this mystification will escalate even more with 1.1.2022 when all my buckets will be fully migrated.
I have no other option then report this repository, until this/similar change will be implemented. There were enough time to implement this.
You are effectively mystifying scoop users that they can use my personal and shovel-org buckets, which is not true in most cases.
Actually, you're the one who's misleading Scoop users. If you want to get excluded from discovery by Scoop users, remove the tags 'scoop-bucket' and any substring 'scoop' from all your repos, along with any redirections. Otherwise Scoop people will keep having the misfortune of having to deal with you.
Once you remove these strings, scoop-directory's inclusion list will get updated automatically.
No it will not be. My buckets are hardcoded
The list was generated programmatically at some point, because your repo contained the substring/tag as I mentioned. Remove the tags/strings/references, and your buckets will get removed once the list is regenerated at some point in the future.
Original issue text:
Closing mysterious issue.
I do not want to be listed as contributor. Implement it on your own and close this PR