Want to make a general issue to publicly list some plans and thoughts we/I have regarding the future of userstyles. The following list will be updated somewhat frequently as I get through the list :)

Todos

High

• Review backlog of init PRs: https://github.com/catppuccin/userstyles/pulls?q=is%3Apr+is%3Aopen+-label%3A%222.status%3A+changes-requested%22+draft%3Afalse+feat+init+sort%3Acreated-asc+-label%3A%222.status%3A+pending%22+.
• Add library modules (Add standard library and modules #1844)
• docs: add userstyles style guide #2046
• docs: cover unspoken rules #2005
• Develop custom installation workflow for userstyles on website #1950

Medium

• Upload userstyles to userstyles.world automatically (Upload to userstyles.world #1392).

Low

• Investigate providing a side-by-side configuration for Dark Reader users (ci: add script to generate dark reader ignore configuration #967).

Unprioritized

• Custom userstyles bot

  I would like to look into a "userstyles bot" that manages the following, as our CI and what GitHub offers isn't ideal.

  • Ping maintainers on issues for their userstyles.
  • Request maintainer reviews for pull requests on their userstyles (replacing CODEOWNERS).
    • Don't request maintainer reviews if the pull request modifies more than, say, 5 userstyles, and/or the pull request is titled with tree-wide. Leave comment noting this, and:
    • Provide command for staff for pinging maintainers on tree-wides. (@catppuccin/userstyles-bot ping tree-wide?)
  • Label pull requests (replacing other messy labeler stuff).
  • Request staff reviews (individually, not whole team) for init pull requests.
  • Provide command for merging pull requests, similar to https://github.com/NixOS/nixpkgs-merge-bot. (@catppucicn/userstyles-bot merge?)
    • Verify that user pinging bot is on userstyles-maintainers team.
    • Verify that pull request only modifies files for their userstyle(s).
    • Maintainers should not be able to use the bot to merge init pull requests.
    • Verifies the commit message is appropriate.
    • Verifies all checks have passed and all staff members have approved.
  • Use for CI, add as exception to branch rules, avoid USERSTYLES_TOKEN and infinite loop mess.
    • Push formatting, health file, and version bump changes to pull request right before merging? Avoids extra commits by squashing with init PR commit.