payloadcms / payloadcms/website
Creating new cloud account didn't redirect to /authorize
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 634
- Forks
- 195
- Avg merge
- 11h 43m
- Merged PRs (30d)
- 17
Description
When creating a new cloud account I left the Github Scope dropdown blank since it wasn't required, but got an error. Am wondering if the dropdown should be marked as required or if connecting Github as a first step should be made more obvious.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing cloud account creation with the Github Scope dropdown left blank and observe the error instead of the expected /authorize redirect. Determine whether the dropdown must be required or whether connecting Github should be made clearer, then verify that the chosen behavior no longer blocks account creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, nextjs, react, typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100