-
Notifications
You must be signed in to change notification settings - Fork 269
Address disabled workflows #4907
Copy link
Copy link
Open
Labels
💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🔒 staff onlyRestricted to staff membersRestricted to staff members🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧰 goal: internal improvementImprovement that benefits maintainers, not usersImprovement that benefits maintainers, not users🧱 stack: mgmtRelated to repo management and automationsRelated to repo management and automations
Description
Metadata
Metadata
Assignees
Labels
💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🔒 staff onlyRestricted to staff membersRestricted to staff members🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧰 goal: internal improvementImprovement that benefits maintainers, not usersImprovement that benefits maintainers, not users🧱 stack: mgmtRelated to repo management and automationsRelated to repo management and automations
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
📋 Backlog
Current Situation
This file exists, but I'm not sure what it's for: https://github.com/WordPress/openverse/blob/f54612d09906e27470ee4c6ad105be707b7da91c/.github/workflows-disabled/sentry-release.yml
The README in the same directory suggests we should enable the workflow after the monorepo migration, but we finished that a long time ago. Do we still need this @dhruvkb? Or can we remove it?
Suggested Improvement
Enable the workflow again or remove the
workflows-disableddirectory and its contents.Benefit
Address unused code.