MADE A SCHEDULE PAGE

[RAJIV81205]

Pull Request Template for GSoC 2024

Related Issue #187

MADE A SCHEDULE PAGE

closes:

Description of Changes

[Provide a concise description of the changes introduced by this PR, detailing what’s been added, modified, or fixed.]

Type of Pull Request

• Bug Fix
• New Feature
• Performance Improvement
• Documentation Update
• Code Refactoring
• Security Enhancement
• Other (Specify): _______________

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

Screenshots / Demo (if applicable)

Train.Timetable.-.Brave.2024-10-13.17-05-29.mp4

Checklist for Contributor

use'X' in [ ] to check it .

• I have reviewed my code before submission.
• I have read and followed the project's Contribution Guidelines.
• I have tested the code thoroughly.
• I have attached related issue numbers, screenshots, or videos (if applicable).
• I have added comments to my code where necessary for clarity.
• I have checked the existing code base and my changes do not introduce any breaking changes.
• My PR addresses only one issue; I have created separate PRs for other issues.
• I have ensured that the PR does not include unrelated files.
• 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

2. 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.

3. 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!

[vercel]

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 13, 2024 0:23am

[github-actions]

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! 😊

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	RapidAPI Key	60a37f5	app.js	View secret
-	-	RapidAPI Key	60a37f5	app.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[dhairyagothi]

Bro @RAJIV81205 this is react page please do it accoeding to that

[haseebzaki-07]

@dhairyagothi please assign me this issue!!