chore: Add labeler #264

Merged

jank merged 2 commits from labeler into main 2025-06-03 07:23:14 +00:00

Conversation 3 Commits 2 Files changed 2 +23

jank commented 2025-06-02 12:45:07 +00:00

Owner

Copy link

No description provided.

jank added 1 commit 2025-06-02 12:45:08 +00:00

chore: Add labeler 536008bab4

Claude commented 2025-06-02 12:46:11 +00:00

Collaborator

Copy link

Code Review Summary

Good addition for automated PR labeling! However, there are a few issues that need attention:

Issues:

1. **** - Incorrect trigger syntax. Should use object format: instead of array format
2. **** - may not be compatible with Gitea Actions. Please verify this GitHub Action works in Gitea environment
3. **** - The nested structure seems unnecessarily complex for simple path matching

Suggestions:

• Test the workflow in Gitea to ensure compatibility
• Consider simplifying the labeler config structure if possible
• Verify the action reference works with Gitea Actions

The concept is excellent for PR organization, just needs these technical fixes for proper functionality.

**Code Review Summary** Good addition for automated PR labeling! However, there are a few issues that need attention: **Issues:** 1. **** - Incorrect trigger syntax. Should use object format: instead of array format 2. **** - may not be compatible with Gitea Actions. Please verify this GitHub Action works in Gitea environment 3. **** - The nested structure seems unnecessarily complex for simple path matching **Suggestions:** - Test the workflow in Gitea to ensure compatibility - Consider simplifying the labeler config structure if possible - Verify the action reference works with Gitea Actions The concept is excellent for PR organization, just needs these technical fixes for proper functionality.

Claude commented 2025-06-02 12:46:18 +00:00

Collaborator

Copy link

Code Review Summary: Good addition for automated PR labeling! However, there are a few issues that need attention. Issues: 1) labeler.yml line 3 - Incorrect trigger syntax, should use object format instead of array format. 2) labeler.yml line 12 - actions/labeler@v5 may not be compatible with Gitea Actions. 3) labeler.yml lines 3-4, 7-8 - The nested any-glob-to-any-file structure seems unnecessarily complex. Suggestions: Test the workflow in Gitea to ensure compatibility and consider simplifying the config structure. The concept is excellent for PR organization, just needs these technical fixes.

Code Review Summary: Good addition for automated PR labeling! However, there are a few issues that need attention. Issues: 1) labeler.yml line 3 - Incorrect trigger syntax, should use object format instead of array format. 2) labeler.yml line 12 - actions/labeler@v5 may not be compatible with Gitea Actions. 3) labeler.yml lines 3-4, 7-8 - The nested any-glob-to-any-file structure seems unnecessarily complex. Suggestions: Test the workflow in Gitea to ensure compatibility and consider simplifying the config structure. The concept is excellent for PR organization, just needs these technical fixes.

jank force-pushed labeler from 536008bab4 to 497910d172 2025-06-02 12:50:35 +00:00 Compare

jank force-pushed labeler from 497910d172 to bc36c1f7fe 2025-06-02 12:51:46 +00:00 Compare

jank force-pushed labeler from bc36c1f7fe to 186a865231 2025-06-02 12:56:14 +00:00 Compare

jank added 1 commit 2025-06-03 06:16:48 +00:00

Merge branch 'main' into labeler 780a360f03

jleibl approved these changes 2025-06-03 07:07:05 +00:00

jank merged commit 684c25b562 into main 2025-06-03 07:23:14 +00:00

jank deleted branch labeler 2025-06-03 07:23:15 +00:00

jank referenced this pull request from a commit 2025-06-03 07:23:16 +00:00

Merge pull request 'chore: Add labeler' (!264) from labeler into main

Commenting is not possible because the repository is archived.

Reviewers

No reviewers

jleibl

Labels

Clear labels   

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

  

backend

  

ci

  

docs

  

frontend

  

lgtm

blocked

  

lgtm

done

  

lgtm

need 1

  

size

huge

  

size

large

  

size

medium

  

size

small

No labels

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Abandoned

Status

Blocked

Status

Need More Info

backend

ci

docs

frontend

lgtm

blocked

lgtm

done

lgtm

need 1

size

huge

size

large

size

medium

size

small

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: SZUT/casino#264

No description provided.