Skip to content

Automatically add ECSoC26 and level labels (ECSoC26-L1, ECSoC26-L2, ECSoC26-L3) to Pull Requests #21

Description

@krishkhinchi

Problem

Pull Requests related to ECSoC26 currently require maintainers to manually assign the event label (ECSoC26) and the corresponding difficulty level label (ECSoC26-L1, ECSoC26-L2, or ECSoC26-L3). This manual process is repetitive and can lead to inconsistent labeling.

Proposed Solution

Implement an automated workflow that adds labels to Pull Requests based on the selected difficulty level.

Expected Behavior

  • Every ECSoC26 Pull Request should automatically receive:
    • ECSoC26
    • One of:
      • ECSoC26-L1
      • ECSoC26-L2
      • ECSoC26-L3

Acceptance Criteria

  • PRs are automatically labeled without maintainer intervention.
  • ECSoC26 is always added to ECSoC26 PRs.
  • Exactly one difficulty label (ECSoC26-L1, ECSoC26-L2, or ECSoC26-L3) is applied.
  • The workflow should not overwrite unrelated existing labels.

Benefits

  • Reduces manual effort for maintainers.
  • Ensures consistent labeling across all ECSoC26 Pull Requests.
  • Improves filtering, tracking, and project management.

Metadata

Metadata

Assignees

Labels

GitHub ActionsGitHub Actions workflows and CI/CDassignedIndicates that the issue has been assigned to a contributor who is actively working on it.enhancementNew feature or requestgithub-actionsGitHub Actions workflows and CI/CDtype:featureIntroduces a new feature or enhancement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions