Implement responsive Navbar with mobile support#440
Open
Dippp10-ally wants to merge 1 commit into
Open
Conversation
Contributor
|
@Dippp10-ally is attempting to deploy a commit to the Vikas' projects Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
@ItsVikasA ji , do assign labels called as gssoc:approved , level:intermediate , type:feature , quality:exceptional to pull request number 440....do merge above pull request number 440..... |
Author
|
@ItsVikasA ji , below are screenshots prior to making changes..... |
Author
|
@ItsVikasA ji , below are screenshots after making changes ..... |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.




🔗 Which issue does this PR close?
📌 Rationale for this change
This change is proposed to improve code quality, usability, or functionality by addressing the issue described in the linked ticket. It helps improve user experience, maintainability, or performance depending on the context of the change.
If the reasoning is already well explained in the issue, this section can be considered optional.
🛠 What changes are included in this PR?
🧪 Are these changes tested?
Testing Details (if applicable)
👉 If no tests are included:
Explain why testing is not required or how the change is covered by existing tests.
👀 Are there any user-facing changes?
If Yes:
Documentation Updates (if needed)
💡 Additional Notes