-
Notifications
You must be signed in to change notification settings - Fork 108
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
event section modified #424
base: main
Are you sure you want to change the base?
Conversation
@Pragati-3003 is attempting to deploy a commit to the unikonf-vibey Team on Vercel. A member of the Team first needs to authorize it. |
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.
Thank you for creating a pull request for vibey!
We appreciate your contribution and are excited to review your changes. If you have any questions or need additional information, please don't hesitate to let us know. We look forward to working with you to improve vibey. Thanks again for your support!If you want to keep contributing to open source and want to do it with a supportive and inclusive community, consider joining UniKonf. We help and encourage each other to make regular contributions to open source projects. If you have any questions, do not hesitate to ask. We look forward to having you as part of our community!
@Pragati-3003 there are some conflicts so have a look into it. |
I am unable to resolve the conflicts as the "Resolve conflicts" button seems to disable. |
@Pragati-3003 you have to resolve the conflicts locally. |
okie |
@Pragati-3003 if you face any difficulty let me know |
@Pragati-3003 any update ? |
@Pragati-3003 please resolve this conflict. |
i have updated the Ui of the card of the events section.
Closes: #332
Type of change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
[ x] Code style update (formatting, local variables)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation update.
This change requires a documentation update
[ x] My code follows the guidelines of this project.
[ x] I have performed a self-review of my own code.
I have commented on my code, particularly wherever it was hard to understand.
I have made corresponding changes to the documentation.
My changes generate no new warnings.
I have added tests that prove my fix is effective or that my feature works.
Any dependent changes have been merged and published in downstream modules.
[ x] I agree to follow this project's Code of Conduct