-
Notifications
You must be signed in to change notification settings - Fork 467
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
Create Github Action to update issues with labels #25818
Comments
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
PR: #25834 |
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
…ues involved in release Introducing release steps to remove label from issues with 'Next Release' and 'Release yy.mm.dd' label to such. Refs: #25818
Here’s the idea for improving our release labeling process: Currently, when an issue is passed, we add the For automation, we could either take all cards with the The goal is to automate this process so these label changes happen automatically when the release is triggered. |
) According to @bryanboza 's requirements at release time the `Next Release` label should be renamed to the release version one and a new `Next Release` label should be created.
This is now working, but we need to set the label color to Also, the label should be "Release : 24.11.29" we are currently missing the |
User Story
As a dev-ops, I want to create a GitHub Action to be utilized in the third job of dotCMS core release-process workflow. This action should accept the following inputs:
Acceptance Criteria
dotCMS Version
master
Proposed Objective
Enhance the release process by automating the removal and potential addition of GitHub issue labels during the workflow.
Proposed Priority
Priority 2 - Important
External Links
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
The text was updated successfully, but these errors were encountered: