-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
chore: improve maintenance #3969
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/EmXWoeiAT4VgkKJUBPG7zo94Addp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks awesome! Great job cleaning all this up. Love the little details like the links to the docs for the various labelers, etc.
cc @lluia, @StefanSelfTaught, @ThangHuuVu. This hopefully will help with triaging. |
* chore: clean up stalebot config * chore: introduce issue labeler bot * chore: clean up PR labeler bot * chore: clean up bug report process * chore: add space * chore: add links to docs in provider/adapter issue templates * chore: add triage label to feature request issue template
I cleaned up the following:
CONTRIBUTING.md
file is more prominent, we should link to that instead. This PR does not address that.next-auth
framework agnostic (Vite, Vue, Express...) #2294) other frameworks.Check the labels page for the new and existing labels: https://github.com/nextauthjs/next-auth/labels
What we could do in addition is to create PR templates specific for new providers and adapters with precise checkpoints (testing, expectations, docs, etc). This can be addressed in a subsequent PR.