enforcing labels in PR before merge

[Light2Dark]

📝 Summary

PRs must have a label of type: enhancement','bug','documentation','internal','preview','other

or an error will be raised with message:
"Select at least one label ['enhancement','bug','documentation','internal','preview','other']"

🔍 Description of Changes

📋 Checklist

• I have read the contributor guidelines.
• For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
• I have added tests for the changes made.
• I have run the code and verified that it works as expected.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
marimo-docs	Ready	Preview	Comment	Dec 1, 2025 6:28pm

[mscolnick]

for colocation, maybe this can live with .github/workflows/labeler.yml? maybe its even better to run this after the auto-labeler

[mscolnick]

@manzt what do you think?

[manzt]

Looks great. Do we want to add a other label for things that don't fit with these labels? Right now, anything that isn't explicitly labeled is filed under "other" in the release notes (instead of ignored like with internal).

We don't need to change anything else about the release notes gen because the label is unused, but it could go here.