Point to official next-auth example #22282
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
balazsorban44
requested review from
divmain,
ijjk,
leerob,
lfades,
Timer and
timneutkens
as code owners
leerob
previously approved these changes
Feb 18, 2021
balazsorban44
dismissed stale reviews from leerob and timneutkens
via
ac98a21
Timer
approved these changes
Feb 18, 2021
This was referenced Mar 5, 2021
This was referenced Mar 8, 2021
This was referenced Mar 15, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We would like to maintain a single
next-authexample under our organization. This PR points readers of the Next.js docs to our repository, instead ofwith-next-authAlso, as @kriscarle pointed out in nextauthjs/next-auth#1132 (comment), we should maybe only maintain a single example to be able to keep it up-to-date more easily.