Closed raspberri05 closed 4 days ago
Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "Update userstyles.yml". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Hi! Glad to see someone willing to pick up the Canvas userstyle. Two things here though; for adding yourself as a maintainer, please see https://github.com/catppuccin/userstyles/blob/main/docs/userstylesyml.md#adding-yourself-as-a-maintainer. And in general we'd like to see a few contributions from you to the userstyle first before we bring you on as a maintainer. I'm going to close this for now - feel free to raise a PR fixing any issues you find with the userstyle (e.g. #368) and then we can talk about becoming a maintainer :)
Ok, thank you
I am requesting to become a maintainer for canvas-lms styles. I am adding myself as a maintainer here pursuant to the instructions in the canvas-lms readme for userstyles. (canva-lms styles currently has no active maintainers so I would like to maintain it.