Skip to content
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

added login,register, github oauth, update name passwords #19

Merged
merged 1 commit into from
Nov 16, 2024

Conversation

wpsadi
Copy link
Contributor

@wpsadi wpsadi commented Nov 16, 2024

Pull Request for ml4e 💡

Requesting to submit a pull request to the PyVerse repository.


Issue Title

Please enter the title of the issue related to your pull request.
Enter the issue title here.

  • I have provided the issue title.

Info about the Related Issue

What's the goal of the project?
Describe the aim of the project.

  • I have described the aim of the project.

Name

Please mention your name.
Enter your name here.

  • I have provided my name.

GitHub ID

Please mention your GitHub ID.
Enter your GitHub ID here.

  • I have provided my GitHub ID.

Email ID

Please mention your email ID for further communication.
Enter your email ID here.

  • I have provided my email ID.

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
Enter your participant role here.

  • I have mentioned my participant role.

Closes

Enter the issue number that will be closed through this PR.
Closes: #issue-number

  • I have provided the issue number.

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
Describe your changes here.

  • I have described my changes.

Type of Change

Select the type of change:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, local variables)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Describe how your changes have been tested.
Describe your testing process here.

  • I have described my testing process.

Checklist

Please confirm the following:

  • My code follows the guidelines of this project.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly wherever it was hard to understand.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added things that prove my fix is effective or that my feature works.
  • Any dependent changes have been merged and published in downstream modules.

Copy link

vercel bot commented Nov 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ml4e ❌ Failed (Inspect) Nov 16, 2024 7:51pm

Copy link

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

@wpsadi
Copy link
Contributor Author

wpsadi commented Nov 16, 2024

Vercel — Deployment has failed
this one not on me

Error Description
app/learn/[category]/[subcategory]/page.tsx
Type error: Type '{ params: { category: string; subcategory: string; }; }' does not satisfy the constraint 'PageProps'.
Types of property 'params' are incompatible.
Type '{ category: string; subcategory: string; }' is missing the following properties from type 'Promise': then, catch, finally, [Symbol.toStringTag]

Person working on /learn page didn't check for error before pushing the code

@aayank13 aayank13 merged commit 2b49f99 into aayank13:main Nov 16, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants