Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cfg value to make ban reasons compulsory #5

Closed
GoogleCodeExporter opened this issue Nov 8, 2015 · 1 comment
Closed

Cfg value to make ban reasons compulsory #5

GoogleCodeExporter opened this issue Nov 8, 2015 · 1 comment
Labels
auto-migrated Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

There are quite a few admins who make bans based on insufficient reasons,
so it would be helpful if there was an option to make the ban reason
compulsory, so that it may be easier to review bans.

Original issue reported on code.google.com by FrancisL...@gmail.com on 5 Nov 2008 at 5:14
@GoogleCodeExporter
Copy link
Author 

I don't see this feature being used by more than a very small handful of 
people. You
should make it clear to your admins that you require a ban reason to be 
entered. If
you want the bot to refuse to store bans with empty reasons you can modify the 
source
code to do so.

Original comment by hogantp on 7 Nov 2008 at 5:24

  • Changed state: WontFix
  • Added labels: Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter