Skip to content

chore: add actions label to labeler and release drafter configurations #46

New issue

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

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 6, 2025

Conversation

FidelusAleksander
Copy link
Contributor

Changes

Checklist

  • I have added or updated appropriate labels to this PR
  • I have tested my changes
  • I have updated the documentation if needed

@Copilot Copilot AI review requested due to automatic review settings May 6, 2025 13:10
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a new "Actions" label for both the release drafter and labeler configurations.

  • Adds an "Actions" category with appropriate icon and label in .github/release-drafter.yml.
  • Configures .github/labeler.yml to detect changes in the actions directory using a glob pattern.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/release-drafter.yml Added a new "Actions" category and updated quoting for consistency.
.github/labeler.yml Introduced a configuration block to label changes in the actions directory.

@github-actions github-actions bot added the maintenance Maintenance work on the repository label May 6, 2025
@FidelusAleksander FidelusAleksander merged commit 269f201 into main May 6, 2025
6 checks passed
@FidelusAleksander FidelusAleksander deleted the add-actions-label branch May 6, 2025 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Maintenance work on the repository
Development

Successfully merging this pull request may close these issues.

1 participant