Implement Sign-In/Sign-Up Page

[Vaibhav22p-qw]

**Fixed issue #268 **

bandicam.2024-05-24.06-48-27-241.mp4

[Anishkagupta004]

It's RAPIDOC spelling mistake

[Vaibhav22p-qw]

hello @Anishkagupta04 done

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

Commits

Files that changed from the base of the PR and between 7eaefe2 and 3724fd1.

Files ignored due to path filters (9)

• assets/img/about.png is excluded by !**/*.png
• assets/img/rd.png is excluded by !**/*.png
• assets/img/rd1.png is excluded by !**/*.png
• assets/img/s1.jpg is excluded by !**/*.jpg
• assets/img/s2.jpg is excluded by !**/*.jpg
• assets/img/s3.jpg is excluded by !**/*.jpg
• assets/img/sec.png is excluded by !**/*.png
• log/favicon.ico is excluded by !**/*.ico
• log/image.gif is excluded by !**/*.gif

Files selected for processing (26)

• • fonts.txt (1 hunks)
• • read me.txt (1 hunks)
• assets/css/styles.css (1 hunks)
• assets/js/main.js (1 hunks)
• assets/scss/base/_base.scss (1 hunks)
• assets/scss/components/_about.scss (1 hunks)
• assets/scss/components/_app.scss (1 hunks)
• assets/scss/components/_buttons.scss (1 hunks)
• assets/scss/components/_contact.scss (1 hunks)
• assets/scss/components/_footer.scss (1 hunks)
• assets/scss/components/_header.scss (1 hunks)
• assets/scss/components/_home.scss (1 hunks)
• assets/scss/components/_mediaqueries.scss (1 hunks)
• assets/scss/components/_scroll.scss (1 hunks)
• assets/scss/components/_security.scss (1 hunks)
• assets/scss/components/_services.scss (1 hunks)
• assets/scss/config/_variables.scss (1 hunks)
• assets/scss/layout/_layout.scss (1 hunks)
• assets/scss/styles.scss (1 hunks)
• assets/scss/theme/_theme.scss (1 hunks)
• dex.html (1 hunks)
• index.html (1 hunks)
• log/login.css (1 hunks)
• log/script.js (1 hunks)
• login.html (1 hunks)
• style.css (1 hunks)

 ________________________
< GLaDOS? I can fix her! >
 ------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Vaibhav22p-qw]

hello @varshith257 & @Anishkagupta004 issue fix #277

bandicam.2024-05-24.13-23-11-029.mp4

[Vaibhav22p-qw]

hello @varshith257 & @Anishkagupta004 both issue fixed #268 & #277 done

[Vaibhav22p-qw]

hello @varshith257 & @Anishkagupta004 both issue fixed #268 & #277 done
Please merge
Gssoc'24

[varshith257]

hello @varshith257 & @Anishkagupta004 both issue fixed #268 & #277 done
Please merge
Gssoc'24

Pull the latest upstream to avoid the others commits into your PR

[Vaibhav22p-qw]

hello @varshith257 7 @Anishkagupta004 Done

[varshith257]

@Vaibhav22p-qw Resolve the conflicts. How can the two issues work be labeled here? Can create a small PR updating readme?

Will label there one of the issues work done here to that PR.

Thanks, this looks good for me

[Vaibhav22p-qw]

Hello @varshith257 make 1 label only merge both

[varshith257]

Can resolve the conflicts?

[Vaibhav22p-qw]

Hello @varshith257 plz assist me how to do

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
rapidoc	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 1, 2024 11:46am

[varshith257]

I have solved it

[github-actions]

🎉 Your pull request has been successfully merged! 🎉 Thank you for your contribution to our project. Your efforts are greatly appreciated. Keep up the fantastic work! 🚀