4 ms·
Tea seems well intentioned but ultimately is going to suffer the same fate as every crypto project: abuse by bad faith actors. Idea: GitHub should let you filt
by dcchambers 3y ago
Tea seems well intentioned but ultimately is going to suffer the same fate as every crypto project: abuse by bad faith actors.
Idea: GitHub should let you filter/block PRs that add or modify certain files. Set up the filter and forget about it, no need to close each PR.
- orangea 3y agoThat is almost certainly possible with github actions.
- dcchambers 3y agoYes, you could set one up to auto-close Pars based on certain filters. Would be nice to prevent them from being opened in the first place.
- devshogun 3y agoHere's a workflow I created to do just that. https://github.com/michaelessiet/tea.yaml-pr-workflow/blob/main/workflow.yaml https://github.com/michaelessiet/tea.yaml-pr-workflow/blob/m...
- dymk 3y agoGithub should consider this a coordinated spam effort, and (shadow)ban accounts which create PRs consisting of only a `mikotea9` or `tea.yaml` file
- dcchambers 3y agoWell first, the file is usually called `tea.yaml` - and the other PRs show that. Not sure why this guy named his file mikotea9... I agree in cases like this GitHub should take action, but in general it would be nice to let people set their own filters as it allows maintainers to prevent abuse more specific to their project, instead of letting GitHub themselves chase things around, and makes it easy to fix the next major spam event that comes around.
- ambigious7777 3y agoThis stuff is pretty similar to the Hacktoberfest incident. Well intentioned projects/events being misused.