hotfix/workflow-duplication #21
@@ -1,42 +1,57 @@
|
||||
|
|
||||
name: AI Chat (Bartender)
|
||||
|
||||
# WORKFLOW ROUTING:
|
||||
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# This workflow handles FREE-FORM questions/chat (no specific command)
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# Other workflows: ai-issue-triage.yml (@codebot triage), ai-comment-reply.yml (specific commands)
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# This is the FALLBACK for any @codebot mention that isn't a known command
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
on:
|
||||
issue_comment:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
types: [created]
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
issue_comment:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
types: [created]
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
# CUSTOMIZE YOUR BOT NAME:
|
||||
# Change '@ai-bot' below to match your config.yml mention_prefix
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# Change '@codebot' in all conditions below to match your config.yml mention_prefix
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# Examples: '@bartender', '@uni', '@joey', '@codebot'
|
||||
|
||||
jobs:
|
||||
ai-chat:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# Only run if comment mentions the bot
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
if: contains(github.event.comment.body, '@codebot') # <-- Change this to your bot name
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
runs-on: ubuntu-latest
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
steps:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- uses: actions/checkout@v4
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
ai-chat:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# Only run if comment mentions the bot but NOT a specific command
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
# This prevents duplicate runs with ai-comment-reply.yml and ai-issue-triage.yml
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
if: |
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
contains(github.event.comment.body, '@codebot') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot triage') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot help') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot explain') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot suggest') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot security') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot summarize') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot review-again') &&
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
!contains(github.event.comment.body, '@codebot setup-labels')
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
runs-on: ubuntu-latest
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
steps:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- uses: actions/checkout@v4
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
- uses: actions/checkout@v4
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
with:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
repository: Hiddenden/openrabbit
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
path: .ai-review
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
token: ${{ secrets.AI_REVIEW_TOKEN }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- uses: actions/checkout@v4
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
with:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
repository: Hiddenden/openrabbit
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
path: .ai-review
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
token: ${{ secrets.AI_REVIEW_TOKEN }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
- uses: actions/setup-python@v5
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
with:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
python-version: "3.11"
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- uses: actions/setup-python@v5
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
with:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
python-version: "3.11"
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
- run: pip install requests pyyaml
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- run: pip install requests pyyaml
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
- name: Run AI Chat
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
env:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_REPO: ${{ gitea.repository }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
SEARXNG_URL: ${{ secrets.SEARXNG_URL }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
run: |
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
cd .ai-review/tools/ai-review
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
python main.py comment ${{ gitea.repository }} ${{ gitea.event.issue.number }} "${{ gitea.event.comment.body }}"
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
- name: Run AI Chat
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
env:
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_REPO: ${{ gitea.repository }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
SEARXNG_URL: ${{ secrets.SEARXNG_URL }}
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
run: |
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
cd .ai-review/tools/ai-review
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
python main.py comment ${{ gitea.repository }} ${{ gitea.event.issue.number }} "${{ gitea.event.comment.body }}"
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
|
||||
|
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow. Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability. **[LOW] Maintainability**
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
**Recommendation:** Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
Bartender
commented
[LOW] Maintainability The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve. Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows. **[LOW] Maintainability**
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
**Recommendation:** Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
|
||||
@@ -1,17 +1,30 @@
|
||||
name: AI Comment Reply
|
||||
|
||||
# WORKFLOW ROUTING:
|
||||
# This workflow handles SPECIFIC commands: help, explain, suggest, security, summarize, review-again, setup-labels
|
||||
# Other workflows: ai-issue-triage.yml (@codebot triage), ai-chat.yml (free-form questions)
|
||||
|
||||
on:
|
||||
issue_comment:
|
||||
types: [created]
|
||||
|
||||
# CUSTOMIZE YOUR BOT NAME:
|
||||
# Change '@ai-bot' below to match your config.yml mention_prefix
|
||||
# Change '@codebot' in the 'if' condition below to match your config.yml mention_prefix
|
||||
# Examples: '@bartender', '@uni', '@joey', '@codebot'
|
||||
|
||||
jobs:
|
||||
ai-reply:
|
||||
runs-on: ubuntu-latest
|
||||
if: contains(github.event.comment.body, '@codebot') # <-- Change this to your bot name
|
||||
# Only run for specific commands (not free-form chat or triage)
|
||||
# This prevents duplicate runs with ai-chat.yml and ai-issue-triage.yml
|
||||
if: |
|
||||
(contains(github.event.comment.body, '@codebot help') ||
|
||||
contains(github.event.comment.body, '@codebot explain') ||
|
||||
contains(github.event.comment.body, '@codebot suggest') ||
|
||||
contains(github.event.comment.body, '@codebot security') ||
|
||||
contains(github.event.comment.body, '@codebot summarize') ||
|
||||
contains(github.event.comment.body, '@codebot review-again') ||
|
||||
contains(github.event.comment.body, '@codebot setup-labels'))
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
||||
|
||||
@@ -1,5 +1,9 @@
|
||||
name: AI Issue Triage
|
||||
|
||||
# WORKFLOW ROUTING:
|
||||
# This workflow handles ONLY the 'triage' command
|
||||
# Other workflows: ai-comment-reply.yml (specific commands), ai-chat.yml (free-form questions)
|
||||
|
||||
on:
|
||||
issue_comment:
|
||||
types: [created]
|
||||
|
||||
17
CLAUDE.md
@@ -186,14 +186,21 @@ Optional:
|
||||
|
||||
## Workflow Architecture
|
||||
|
||||
Workflows are located in `.gitea/workflows/`:
|
||||
Workflows are located in `.gitea/workflows/` and are **mutually exclusive** to prevent duplicate runs:
|
||||
|
||||
- **ai-review.yml** / **enterprise-ai-review.yml** - Triggered on PR open/sync
|
||||
- **ai-issue-triage.yml** - Triggered on `@codebot triage` mention in issue comments
|
||||
- **ai-comment-reply.yml** - Triggered on issue comments with @bot mentions
|
||||
- **ai-chat.yml** - Triggered on issue comments for chat (non-command mentions)
|
||||
- **enterprise-ai-review.yml** - Triggered on PR open/sync
|
||||
- **ai-issue-triage.yml** - Triggered ONLY on `@codebot triage` in comments
|
||||
- **ai-comment-reply.yml** - Triggered on specific commands: `help`, `explain`, `suggest`, `security`, `summarize`, `review-again`, `setup-labels`
|
||||
- **ai-chat.yml** - Triggered on `@codebot` mentions that are NOT specific commands (free-form questions)
|
||||
- **ai-codebase-review.yml** - Scheduled weekly analysis
|
||||
|
||||
**Workflow Routing Logic:**
|
||||
1. If comment contains `@codebot triage` → ai-issue-triage.yml only
|
||||
2. If comment contains specific command (e.g., `@codebot help`) → ai-comment-reply.yml only
|
||||
3. If comment contains `@codebot <question>` (no command) → ai-chat.yml only
|
||||
|
||||
This prevents the issue where all three workflows would trigger on every `@codebot` mention, causing massive duplication.
|
||||
|
||||
**Note**: Issue triage is now **opt-in** via `@codebot triage` command, not automatic on issue creation.
|
||||
|
||||
Key workflow pattern:
|
||||
|
||||
[LOW] Maintainability
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
[LOW] Maintainability
The 'if' condition for filtering out specific commands in the ai-chat workflow is very long and repetitive, which could be error-prone and hard to maintain as commands grow.
Recommendation: Consider defining a reusable list of commands and using a function or expression to check for exclusion, or move this logic to a reusable script or action input to improve maintainability.
[LOW] Maintainability
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.
[LOW] Maintainability
The workflow condition for ai-chat.yml uses a long chain of negated contains() checks to exclude specific commands, which can be error-prone and hard to maintain as commands evolve.
Recommendation: Consider defining a reusable list or variable of known commands and use a more maintainable expression or a script step to determine if the comment is a free-form chat. Alternatively, centralize command definitions to avoid duplication across workflows.