add ci to options for label checker categories

[gforsyth]

I opened a PR over on dask-cuda and didn't see a ci label listed as an option to pass the label-checker, but it seems like it does exist.

Not sure if it's universal across RAPIDS repos, but if it is, it should be added to this page.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Dec 13, 2024 7:40pm

[netlify]

✅ Deploy Preview for docs-rapids-ai ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	e54c6e3
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rapids-ai/deploys/675c8d77f356c20008c1ad43
😎 Deploy Preview	https://deploy-preview-564--docs-rapids-ai.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bdice]

The allowed list of labels is here: https://github.com/rapidsai/ops-bot/blob/fdeb43f78722173f39944d331ac36cff52594c61/src/plugins/LabelChecker/label_checker.ts#L61

ci is an informational label but not a permitted category, so the label checker will fail. This category information is used to generate changelogs.

Every RAPIDS library PR must be one marked with one of the listed categories, and breaking or non-breaking.

[gforsyth]

Ahh, ok, thanks for clarifying. Do you think adding a ci category makes sense?

[bdice]

Ahh, ok, thanks for clarifying. Do you think adding a ci category makes sense?

Usually we just put build-related changes in “improvement.” Calling out CI changes in the changelog is probably not that useful, as it won’t affect library users directly.