Skip to content
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

[FEATURE] Mandatory labeling for PRs #1281

Closed
Swiddis opened this issue Dec 1, 2023 · 0 comments · Fixed by #1292
Closed

[FEATURE] Mandatory labeling for PRs #1281

Swiddis opened this issue Dec 1, 2023 · 0 comments · Fixed by #1292
Assignees
Labels
enhancement New feature or request

Comments

@Swiddis
Copy link
Collaborator

Swiddis commented Dec 1, 2023

Is your feature request related to a problem?
Most OpenSearch repositories, including this one, have an action that automatically drafts release notes as PRs are merged. Since we typically don't label our PRs, this feature isn't seeing usage, and slowing down release note processes.

What solution would you like?
In the name of not relying on everyone to start automatically, I propose introducing a CI check that mandates labeling PRs. This is already used in the observability repo and by & large makes the generation process easier.

What alternatives have you considered?
The main alternative is manually applying them without any strict checks, which could theoretically work (and would more flexibly allow deliberately ignoring inconsequential PRs in release notes), but doesn't seem to be applied.

Do you have any additional context?
Read about release-drafter, Ashwin's Proposal for automating release notes based on labels, or the WIP PoC for release note generation in OSD.

@Swiddis Swiddis added enhancement New feature or request untriaged and removed untriaged labels Dec 1, 2023
@Swiddis Swiddis mentioned this issue Dec 7, 2023
6 tasks
@Swiddis Swiddis self-assigned this Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant