[Task] 🛠️ Chore | Enhancement: Automate and generate Labels from `yaml` for Issues and PRs.

[iPoetDev]

Task Topic

Automations

Task Description

Request: Automate and generate Labels from yaml configuration files in lieu of the burden of manual definition, creation, editing, removal.

How: By a GitHub Action

• GitHub Action
• GitHub App
• External Service

1. Select from GitHub Marketplace
2. Select from other GitHub action source
3. Roll your own action.

Use Case

Problem to Solve

• Manually re-creating labels per repository
• Customising longer inventory of labels
• Utilising labels for more descriptive context / categorisation for search and individual preference.
• Utilising labels to automate workflow and issue lifecycle (state, status, stage, priority, severity).

User Story

Context	Description
As a	maintainer of a GitHub repository
I/we want	to manage the lifecycle of issues by workflow automation
So that	to reduce manual effort in creating, reading/defining context, modifying, and removing or deprecating

Additional Information

Proposed Global Candidate Labels

Name	Color	Description	Aliases
✨ good first issue	5319e7	✨ Good for newcomers	beginner, easy
🆘 help wanted	008672	🆘 Extra attention is needed	assistance, need help
⏳ status: pending	c5def5	⏳ More info is needed before deciding what to do	awaiting response, waiting
📌 status: pinned	0052cc	📌 Should not be labeled as stale	important, 🛑 dont close
🕰️ status: stale	fbca04	🕰️ Inactive issues and PRs	stale
🚫 status: wontfix	cfd3d7	🚫 This will not be worked on	wontfix, not going to fix
🐛 type: bug	d73a4a	🐛 Verified problems that need to be worked on	bug, defect
🔧 type: chore	C5DEF5	🔧 Code changes: refactoring, dependency changes	dependencies, type: dependencies, automation, type: automation
📚 type: docs	C5DEF5	📚 Documentation changes	documentation, maintenance, type: maintenance
🔄 type: duplicate	cfd3d7	🔄 This issue or pull request already exists	duplicate, already reported
🌟 type: feature	0E8A16	🌟 New feature or feature request	enhancement, type: enhancement, new feature
🔧 type: fix	1D76DB	🔧 Updates to existing functionalities	fix, improvement
❌ type: invalid	e4e669	❌ This doesn't seem right	invalid, not valid
🚫 type: not a bug	0e8a16	🚫 Reports that happen not to be our fault	not a bug, not an issue
❓ type: question	d876e3	❓ Further information is requested	question, inquiry
🔍 type: enhancement	0E8A16	🔍 Improvements to existing features	improvement, feature enhancement
🔬 type: research	f9c2ff	🔬 Research tasks or investigations	investigation, exploration
⚙️ type: performance	ffcc00	⚙️ Performance-related issues or improvements	performance issue, optimization

Priority Labels

Name	Color	Description	Aliases
🚨 priority: high	ff0000	🚨 High priority - needs immediate attention	urgent, critical
⚠️ priority: medium	ffcc00	⚠️ Medium priority - should be addressed soon	normal, moderate
🟢 priority: low	00ff00	🟢 Low priority - can be addressed later	minor, trivial

Severity Labels

Name	Color	Description	Aliases
🔥 severity: critical	ff0000	🔥 Critical severity - major impact on functionality	blocker, severe
⚠️ severity: major	ffcc00	⚠️ Major severity - significant impact but not critical	high impact
🟢 severity: minor	00ff00	🟢 Minor severity - low impact on functionality	low impact, negligible
🔵 severity: trivial	c5def5	🔵 Trivial severity - no significant impact	cosmetic, insignificant