-
Notifications
You must be signed in to change notification settings - Fork 214
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
aligned the return to top arrow #752
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, @DevROHIT11! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.
We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines
✅ Deploy Preview for collect-your-gamingtools ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@swaraj-das it was great to contribute with you , resolving the issue was not that much easy but finally i completed with lots of efforts so could you please merge my pull request ASAP before the merge conflict occur . If possible please label it above level 1 |
Hi there! This issue is still open. We are looking forward to your response. |
@swaraj-das this issue is arise while merging someones PR I check From my side their are no changes happened |
Hi there! This issue is still open. We are looking forward to your response. |
1 similar comment
Hi there! This issue is still open. We are looking forward to your response. |
Hii Gssoc would you please review my PR and merge it I had mentioned the level of each PR below (Level 2) swaraj-das/Collect-your-GamingTools#752 (level 2) swaraj-das/Collect-your-GamingTools#761 (level 3) vishanurag/Canvas-Editor#796
Hi there! This issue is still open. We are looking forward to your response. |
12 similar comments
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
26 similar comments
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Pull Request Format
Aligned the return top arrow
Issue #615 : Return to top arrow and chatbot overlapped solved
Type of PR
Description
This pull request aims to resolved the issue of overlapping of return to top arrow with chatbot which is now resolved
Screenshots / Videos (if applicable)
Before:
After:
Checklist
Thank you for reviewing my pull request!