Skip to content
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

issue51 #74

Closed
wants to merge 1 commit into from
Closed

issue51 #74

wants to merge 1 commit into from

Conversation

ash-k121
Copy link

@ash-k121 ash-k121 commented Oct 5, 2024

Pull Request Template for GSoC 2024

Related Issue

issue no 51

Type of Pull Request

  • New Feature

(Please check relevant boxes by entering an "X" inside them)

image

[Include any screenshots, GIFs, or videos that demonstrate the change or feature, if available.]

Checklist for Contributor

use'X' in [ ] to check it .

  • [ X] I have reviewed my code before submission.
  • [ X] I have read and followed the project's Contribution Guidelines.
  • [ X] I have tested the code thoroughly.
  • [X ] I have attached related issue numbers, screenshots, or videos (if applicable).
  • [ X] I have added comments to my code where necessary for clarity.
  • [X ] I have checked the existing code base and my changes do not introduce any breaking changes.
  • [X ] My PR addresses only one issue; I have created separate PRs for other issues.
  • [ X] I have ensured that the PR does not include unrelated files.
  • [ X] I am mindful of the project's coding standards and best practices.

Additional Information

[Include any additional context or relevant information that may help in reviewing this PR.]

Contribution Guidelines Reminder

Thank you for contributing to our project! Please ensure you follow the guidelines below:

Contribution Levels

  1. Task Categories:

    • Basic Tasks: Primarily focused on small changes like minor bug fixes, documentation improvements, and unit testing. Labeled as Easy.
    • Intermediate Tasks: Moderate-level tasks that involve enhancing existing features, code refactoring, or performance improvements. Labeled as Medium.
    • Advanced Tasks: Complex tasks like building new features, significant refactoring, or critical bug fixes. Labeled as Hard.
  2. Acknowledging Effort:

    • Exceptional contributions will be recognized with a higher contribution level if substantial effort and innovation are demonstrated.

Review Process

  • PRs will be reviewed by the maintainers, and feedback will be provided. Contributors should address feedback promptly and resubmit the PR if necessary.

  • Contributors are encouraged to participate in the review process of other PRs for community growth.

We appreciate your time and effort in improving this project and look forward to your valuable contributions!

Sorry, something went wrong.

Copy link

vercel bot commented Oct 5, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
station-guide ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 5, 2024 7:25pm

Copy link
Contributor

github-actions bot commented Oct 5, 2024

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@dhairyagothi
Copy link
Owner

@ash-k121 there are merge conflicts and we don't want train booking check figma UI we want like that

@ash-k121
Copy link
Author

ash-k121 commented Oct 6, 2024

@ash-k121 there are merge conflicts and we don't want train booking check figma UI we want like that

okay

@dhairyagothi
Copy link
Owner

bro there are multiple conflicts ,....

and please share ss

@ash-k121
Copy link
Author

ash-k121 commented Oct 6, 2024

bro there are multiple conflicts ,....

and please share ss

You can ignore the conflicts in backend package folders (as i was trying to create the user and ticket schema), i have just added a file for ticket schema (backend)and booking page (frontend) and regarding the figma ui i’ll update it asap

@dhairyagothi
Copy link
Owner

bro there are multiple conflicts ,....
and please share ss

You can ignore the conflicts in backend package folders (as i was trying to create the user and ticket schema), i have just added a file for ticket schema (backend)and booking page (frontend) and regarding the figma ui i’ll update it asap

bro without seeing your work and with conflicts PR how can i merge

@ash-k121
Copy link
Author

ash-k121 commented Oct 7, 2024

bro there are multiple conflicts ,....
and please share ss

You can ignore the conflicts in backend package folders (as i was trying to create the user and ticket schema), i have just added a file for ticket schema (backend)and booking page (frontend) and regarding the figma ui i’ll update it asap

bro without seeing your work and with conflicts PR how can i merge

i am not asking you to merge ,i’ll solve the conflicts

@dhairyagothi
Copy link
Owner

bro there are multiple conflicts ,....
and please share ss

You can ignore the conflicts in backend package folders (as i was trying to create the user and ticket schema), i have just added a file for ticket schema (backend)and booking page (frontend) and regarding the figma ui i’ll update it asap

bro without seeing your work and with conflicts PR how can i merge

i am not asking you to merge ,i’ll solve the conflicts

ya bro you solve it but share me some video of your changes

@ash-k121
Copy link
Author

ash-k121 commented Oct 7, 2024

sure

bro there are multiple conflicts ,....
and please share ss

You can ignore the conflicts in backend package folders (as i was trying to create the user and ticket schema), i have just added a file for ticket schema (backend)and booking page (frontend) and regarding the figma ui i’ll update it asap

bro without seeing your work and with conflicts PR how can i merge

i am not asking you to merge ,i’ll solve the conflicts

ya bro you solve it but share me some video of your changes

sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants