fixed the logo problem#99
Merged
Merged
Conversation
|
@Soumyosish is attempting to deploy a commit to the bavanetha27's projects Team on Vercel. A member of the Team first needs to authorize it. |
Thanks for creating a PR for your Issue!
|
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.
🛠️ Pull Request Template
📄 Description
Describe the changes you made and the purpose of this pull request.
I have corrected the file path for the gssoc logo in the readme file.
✅ Checklist
Fixes #issue_no📎 Related Issue
Fixes #98
Please @Bavanetha27 check and merge the PR and add the gssoc25 label along with the level of contribution. Let me know if require any changes.
Hi @Bavanetha27
I have noticed that the CI checks on this PR are failing due to some environment-related issues, such as:
Node.js engine version mismatches (packages requiring Node >= 20, but CI is running Node 18)
Missing dependencies like globals causing ESLint errors
Deprecated packages warnings and related audit vulnerabilities
These errors seem related to the project’s dependency and tooling configurations rather than the code changes I made in this PR.
I wanted to flag this in case you were not yet aware. Please let me know if there are any specific fixes or requires any changes.
I have modified the files which were having unnecessary props, states and solved the errors through vscode
npm run lintcommand but the global CI problems are addressed.