Fix: Update GSSoC year from 2025 to 2026 in README#56
Open
Mohit-001-hash wants to merge 1 commit into
Open
Conversation
|
@Mohit-001-hash is attempting to deploy a commit to the ashishparab03-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
📝 Description
Fixed outdated GSSoC year references in README.md.
The README had three places mentioning GSSoC 2025 which
is outdated — the current program is GSSoC 2026.
Changes made:
🔗 Related Issues
Closes #
🎯 Type of Change
✅ Testing
What testing was done?
How to Test
🔍 Code Review Checklist
📝 Documentation
🚀 Deployment
📋 Additional Notes
Documentation-only change. No code logic affected.