[FEATURE]: Adding a CI/CD workflow to manage Issue and PR labeling

[Yuvraj-Sarathe]

💡 The Pitch

Add an automated workflow for GitHub Actions to add labels on issues and PRs.

🤔 Why do we need this?

To decrease the risk of not adding any labels when merging a PR. This also makes it easier for maintainers.

🛠️ Proposed Solution

Adding a CI/CD pipeline to automate a GitHub Actions bot to add labels in issues and PRs. All files will be under the `.github/ "directory." You can also edit the existing issue and PR templates to have a standard format for GitHub Actions to work with.

Make sure these labels are there:

• ECSoC26
• ECSoC-L1 (or L2 or L3 based on the assessment of the issue, and if PR, then the same labels will move over to PR linked with the issue)
• Features, bugs, documentation, backend, frontend, CI/CD, DevOps, etc. should also be there.

[Yuva-Deekshitha-N]

hi @Yuvraj-Sarathe ! I'd like to work on this issue as part of ECSoC'26.

I plan to:

-Create a GitHub Actions workflow to automatically apply labels to issues and pull requests.
-Ensure all new issues receive the ECSoC26 label.
-Automatically apply the appropriate ECSoC-L1, ECSoC-L2, or ECSoC-L3 label based on the issue.
-Propagate the difficulty label from the linked issue to its corresponding pull request.
-Add labels such as feature, bug, documentation, backend, frontend, CI/CD, DevOps, etc., based on the issue/PR template inputs.
-Update the existing issue and PR templates (if required) to support consistent automatic labelling.

I have experience working with GitHub Actions and would love to contribute this automation.
Could you please assign this issue to me under ECSoC'26?