Is it worth setting across nf-core repos to help c...
# team-maintainers
c
Is it worth setting across nf-core repos to help combat spam? This prevents blank issues from being populated with spam and might help encourage users with genuine issues to open a more structured issue via an issue template.
Copy code
blank_issues_enabled: false
<!subteam^S044DU0NG68> thoughts?
s
what does it do?
m
means you need to use a template.
s
How much spam are we getting?
c
I updated my original message (couldn't find my glasses) It looks like there were 5 or so issues from one user advertising something
😁 1
i
Can you give some examples? I honestly don't recall seeing any spam issues
m
Like the one Matthieu posted above. The user has been blocked, and I think GitHub has already taken action against the user
i
I see the action was so effective that nothing is left of the issues
p
Yeah I think GitHub must have banned him
I personally quite like being able to make blank issues 👀 It's been raised as a suggestion before to try to improve issue quality, but we didn't go for it.
this 4
But that doesn't mean we can't revisit it
🙌 1
c
I agree GH dealt with it quickly so it doesn't really make sense this time, but now I'm interested @Phil Ewels if you don't mind - do you mean for repos in general across GitHub? is this for bug reports or feature requests, or something else? Can the templates be improved? How to balance a low barrier to entry for people to open an issue quickly and easily, while capturing enough info for a maintainer and avoid too many follow-up questions that could have been captured via a template... (this is not specifically an nf-core related question so I'm not in a rush!
Really appreciate any thoughts anyone has