Skip to content

Commit

Permalink
ci(ai): add AI issue templates and pull request labeler
Browse files Browse the repository at this point in the history
This commit introduces two new AI-specific issue templates, aiming to streamline the routing of AI subnet-related issues and feature requests to the appropriate team. It also adds a pull request labeler action that automatically attaches the `ai` label when a pull request is created to the `ai-video` branch.
  • Loading branch information
rickstaa authored Apr 15, 2024
2 parents 52186d7 + c822b13 commit 25c3cd2
Show file tree
Hide file tree
Showing 4 changed files with 144 additions and 4 deletions.
76 changes: 76 additions & 0 deletions .github/ISSUE_TEMPLATE/ai_bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
name: AI Bug report
description: Create a report to help us improve.
labels:
- "bug"
- "ai"
body:
- type: markdown
attributes:
value: |
## Bug report
Please fill out the following information to help us understand your issue.
> [!IMPORTANT]
> This repository is only related to the core bugs with the AI branch of the go-livepeer software (i.e. `ai-video`). It does not cover bugs related to running AI pipelines and AI models used on the AI subnet. For these issues, please refer to the [AI-worker repository](https://github.com/livepeer/ai-worker/issues/new/choose)
- type: textarea
attributes:
label: Describe the bug
description: A clear and concise description of what the bug is.
validations:
required: true
- type: textarea
attributes:
label: Reproduction steps
description: "How do you trigger this bug? Please walk us through it step by step."
value: |
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
- type: textarea
attributes:
label: Expected behaviour
description: A clear and concise description of what you expected to happen.
- type: dropdown
id: severity
attributes:
label: Severity
description: "How severe is this bug?"
options:
- Minor
- Major
- Critical
- type: textarea
attributes:
label: Screenshots / Live demo link
description: If applicable, add screenshots to help explain your problem.
placeholder: Paste the image link as markdown image
- type: dropdown
id: os
attributes:
label: OS
description: "What operating system are you using?"
options:
- Windows
- Mac
- Linux
- type: dropdown
id: running_on
attributes:
label: Running on
description: "Where are you running the application?"
options:
- Local
- Docker
- type: input
attributes:
label: AI go-livepeer version
description: "What version of the AI-worker are you using?"
- type: input
attributes:
label: AI go-livepeer commit hash
description: "Could you please provide the commit hash of the `ai-video` branch that you are currently using?"
- type: textarea
attributes:
label: Additional context
description: Add any other context about the problem here.
45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/ai_feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: AI Feature request
description: Suggest an idea for this project.
labels:
- "enhancement"
- "ai"
body:
- type: markdown
attributes:
value: |
## Feature Request
Please fill out the following information to help us understand your request.
> [!IMPORTANT]
> This repository is only related to feature requests related to the the AI branch of the go-livepeer software (i.e. `ai-video`). It does not cover feature requests related to the addition of new AI pipelines and AI models used on the AI subnet. For these issues, please refer to the [AI-worker repository](https://github.com/livepeer/ai-worker/issues/new/choose).
- type: textarea
attributes:
label: Is your feature request related to a problem? Please describe.
description:
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
validations:
required: true
- type: textarea
attributes:
label: Describe the solution you'd like
description: A clear and concise description of what you want to happen.
- type: textarea
attributes:
label: Describe alternatives you've considered
description:
A clear and concise description of any alternative solutions or features
you've considered.
- type: textarea
attributes:
label: Use Case
description: "Please describe why you want this feature to be added. This will help us prioritize your request."
- type: textarea
attributes:
label: Expected Outcome
description: "What do you expect to happen once this feature is implemented?"
- type: textarea
attributes:
label: Additional context
description:
Add any other context or screenshots about the feature request here.
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
blank_issues_enabled: true
contact_links:
- name: Go-livepeer Question
url: https://github.com/livepeer/go-livepeer/discussions
about: Please ask and answer questions related to the go-livepeer software here.
- name: Livepeer Question
url: https://discord.gg/livepeer
about: "Have a general Livepeer question? Join us in the Livepeer Discord server. We're here to help!"
19 changes: 15 additions & 4 deletions .github/workflows/issue-labeler.yml
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
name: Label issues
name: Label issues and pull requests
on:
issues:
types:
- reopened
- opened
types: [opened, reopened]
pull_request:
types: [opened, reopened]

jobs:
label_issues:
if: ${{ github.event_name == 'issues' }}
runs-on: ubuntu-latest
permissions:
issues: write
Expand All @@ -16,3 +18,12 @@ jobs:
add-labels: "status: triage"
repo-token: ${{ secrets.GITHUB_TOKEN }}
ignore-if-assigned: false

label_pull_requests:
if: ${{ github.event_name == 'pull_request' }}
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write
steps:
- uses: actions/labeler@v5

0 comments on commit 25c3cd2

Please sign in to comment.