aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | | | | * | | | | change: make unban require pardon reasonGravatar Luna2022-08-18-7/+1
| | | | | | | | | |
| | | | | * | | | | add: test for reasoned and reasonless pardonsGravatar Luna2022-08-17-1/+7
| | | | | | | | | |
| | | | | * | | | | fix: trailing whitespaceGravatar Luna2022-08-17-1/+1
| | | | | | | | | |
| | | | | * | | | | Merge pull request #2 from VirdanTheBurden/feat-add-reason-argument-to-pardonsGravatar Luna Ilune Makyus2022-08-17-6/+7
| | | | | |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | fix: docstrings
| | | | | | * | | | | fix: docstringsGravatar Luna2022-08-17-6/+7
| | | | | | | | | | |
| | | | | * | | | | | Merge pull request #1 from VirdanTheBurden/feat-add-reason-argument-to-pardonsGravatar Luna Ilune Makyus2022-08-17-8/+40
| | | | | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | feat: add reason argument to pardon commands
| | | | | | * | | | | fix: lintGravatar Luna2022-08-17-5/+23
| | | | | | | | | | |
| | | | | | * | | | | feat: add reason argument to pardon commandsGravatar Luna2022-08-17-10/+24
| | | | | |/ / / / /
| | | | | | * / / / Remove unnecessary logginGravatar Juan Ignacio Battiston2022-08-28-2/+0
| | | | | |/ / / / | | | | |/| | | |
| | | | | | * | | move DEFAULT_RULES_DESCRIPTION under information.pyGravatar Amrou Bellalouna2022-09-20-9/+7
| | | | | | | | |
| | | | | | * | | use subTest to isolate assertionsGravatar Amrou Bellalouna2022-09-19-14/+17
| | | | | | | | |
| | | | | | * | | add DEFAULT_RULES_DESCRIPTION to avoid duplicationGravatar Amrou Bellalouna2022-09-19-13/+10
| | | | | | | | |
| | | | | | * | | fix redundant test nameGravatar Amrou Bellalouna2022-09-19-1/+1
| | | | | | | | |
| | | | | | * | | test the cases where default rules message is supposed to be sentGravatar Amrou Bellalouna2022-09-19-0/+31
| | | | | | | | |
| | | | | | * | | fix wrong type hint of the rules function return valueGravatar Amrou Bellalouna2022-09-19-2/+2
| | | | | | | | |
| | | | | | * | | add test that checks for the sent content if one invalid index is present in ↵Gravatar Amrou Bellalouna2022-09-19-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the input
| | | | | | * | | return final list of rule numbers to be sentGravatar Amrou Bellalouna2022-09-19-2/+4
| | | | | | | | |
| | | | | | * | | sort the list of final rule numbersGravatar Amrou Bellalouna2022-09-19-1/+1
| | | | | | | | |
| | | | | | * | | determine final_rule_numbers value by subscribing to the ↵Gravatar Amrou Bellalouna2022-09-18-9/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | keyword_to_rule_number using the matched keywords
| | | | | | * | | subscribe directly to the keyword_to_rule_number dict instead of using .getGravatar Amrou Bellalouna2022-09-18-1/+2
| | | | | | | | |
| | | | | | * | | remove redundant use of list transformation when sorting final rule numbersGravatar Amrou Bellalouna2022-09-18-1/+1
| | | | | | | | |
| | | | | | * | | replace the keywords set with a dict that maps each keyword to its rule numberGravatar Amrou Bellalouna2022-09-18-8/+6
| | | | | | | | |
| | | | | | * | | enumerate full_rules with a start index of 1Gravatar Amrou Bellalouna2022-09-18-2/+2
| | | | | | | | |
| | | | | | * | | remove useless initial sorting of keywordsGravatar Amrou Bellalouna2022-09-18-2/+0
| | | | | | | | |
| | | | | | * | | remove duplicate final rule numbers then sortGravatar Amrou Bellalouna2022-09-18-1/+1
| | | | | | | | |
| | | | | | * | | remove unreachable codeGravatar Amrou Bellalouna2022-09-18-8/+0
| | | | | | | | |
| | | | | | * | | rename pick to rule_numberGravatar Amrou Bellalouna2022-09-18-2/+2
| | | | | | | | |
| | | | | | * | | rename index to rule_numberGravatar Amrou Bellalouna2022-09-18-1/+3
| | | | | | | | |
| | | | | | * | | stop matching keywords when they're invalid upon triaging the rule numbers & ↵Gravatar Amrou Bellalouna2022-09-18-19/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | keywords
| | | | | | * | | stop matching as soon as an invalid kw is encounteredGravatar Amrou Bellalouna2022-09-18-11/+22
| | | | | | | | |
| | | | | | * | | remove help message that displays the available keywords per ruleGravatar Amrou Bellalouna2022-09-16-8/+2
| | | | | | | | |
| | | | | | * | | rename rules to rule_numbersGravatar Amrou Bellalouna2022-09-16-7/+7
| | | | | | | | |
| | | | | | * | | replace .isdigit predicate with a try except blockGravatar Amrou Bellalouna2022-09-16-2/+2
| | | | | | | | |
| | | | | | * | | fix typo in docstringsGravatar Amrou Bellalouna2022-09-16-1/+1
| | | | | | | | |
| | | | | | * | | use the cached channels instead of fetching them with each command executionGravatar Amrou Bellalouna2022-09-16-4/+2
| | | | | | | | |
| | | | | | * | | Merge remote-tracking branch 'origin/2108-invoke-rule-command-with-keywords' ↵Gravatar Amrou Bellalouna2022-09-16-0/+0
| | | | | | |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into 2108-invoke-rule-command-with-keywords
| | | | | | | * | | suggest adding a keyword in dev & meta channelsGravatar Amrou Bellalouna2022-09-11-3/+6
| | | | | | | | | |
| | | | | | | * | | add missing blank lineGravatar Amrou Bellalouna2022-09-11-0/+1
| | | | | | | | | |
| | | | | | | * | | accept keywords and rule numbers in any orderGravatar Amrou Bellalouna2022-09-11-19/+39
| | | | | | | | | |
| | | | | | | * | | send the "no-match" error message in pure text formatGravatar Amrou Bellalouna2022-09-08-5/+2
| | | | | | | | | |
| | | | | | | * | | send the list of pre-defined keywords along with each invoked ruleGravatar Amrou Bellalouna2022-09-08-2/+7
| | | | | | | | | |
| | | | | | | * | | add support for keywords when using the "rules" command.Gravatar Amrou Bellalouna2022-08-19-4/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This doesn't change the way the rules command originally worked and keeps the priority to rule numbers. But in case a number (or numbers) is not supplied, it will try to find a rule that maps to a the supplied keyword.
| | | | | | | * | | fix "isistance" typoGravatar Amrou Bellalouna2022-08-19-1/+1
| | |_|_|_|_|/ / / | |/| | | | | | |
| | | | | | * | | suggest adding a keyword in dev & meta channelsGravatar Amrou Bellalouna2022-09-16-3/+6
| | | | | | | | |
| | | | | | * | | add missing blank lineGravatar Amrou Bellalouna2022-09-16-0/+1
| | | | | | | | |
| | | | | | * | | accept keywords and rule numbers in any orderGravatar Amrou Bellalouna2022-09-16-19/+39
| | | | | | | | |
| | | | | | * | | send the "no-match" error message in pure text formatGravatar Amrou Bellalouna2022-09-16-5/+2
| | | | | | | | |
| | | | | | * | | send the list of pre-defined keywords along with each invoked ruleGravatar Amrou Bellalouna2022-09-16-2/+7
| | | | | | | | |
| | | | | | * | | add support for keywords when using the "rules" command.Gravatar Amrou Bellalouna2022-09-16-4/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This doesn't change the way the rules command originally worked and keeps the priority to rule numbers. But in case a number (or numbers) is not supplied, it will try to find a rule that maps to a the supplied keyword.
| | | | | | * | | fix "isistance" typoGravatar Amrou Bellalouna2022-09-16-1/+1
| |_|_|_|_|/ / / |/| | | | | | |