irfan-iiitr commented 4 months ago

Description

In Issue Template and in the workflow of advanced Labeler , The year 2023 was was still used. I updated it to work for 2024.

Pull Request Checklist

Please make sure that your PR meets the following requirements:

[x] The app is working correctly after applying the changes.
[x] The app is responsive and displays properly on different screen sizes and devices.
[x] The changes are thoroughly documented in the appropriate files or documentation sections.
[x] The coding conventions and style guidelines are followed consistently.

Checklist

Please check all applicable boxes and provide any additional information if needed.

[x] I have tested the changes locally and ensured that the app is functioning as expected.
[x] I have verified that the app is responsive and looks good on various screen sizes and devices.
[x] I have reviewed the documentation and ensured that it accurately reflects the changes made.
[x] I have followed the coding conventions and style guidelines defined in the project.
[x] I have run the automated tests and all of them pass.
[x] I have considered the performance implications of the changes made.
[x] I have considered the security implications of the changes made.
[x] I have checked for any potential regressions or side effects caused by the changes.
[x] I have performed a self-review of my code.
[x] Starred the repository.
[ ] Added My Name to the Contributor's List.
[x] Followed the repository's Contributing Guidelines.
[x] I ran the app and tested it locally to verify that it works as expected.

Screenshots - If Any (Optional)

Related Issues

It closes Issue No. #634 and #627 .

Reviewers

Please tag the relevant team members or reviewers who should review this pull request.

vercel[bot] commented 4 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
project-amupedia	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 20, 2024 3:11pm

coderabbitai[bot] commented 4 months ago

Walkthrough

## Walkthrough The primary change involves updating references from "GSSoC2023" to "GSSoC2024" across various GitHub configuration files, including issue templates, advanced labeler configuration, and GitHub Actions workflows. This ensures that all references align with the current year's program. ## Changes | File Path | Change Summary | |---------------------------------------------|-------------------------------------------------------------------------------------| | `.github/ISSUE_TEMPLATE/bug_report.yml` | Updated program option from "GSSoC2023" to "GSSoC2024". | | `.github/ISSUE_TEMPLATE/doc.yml` | Updated program option from "GSSoC2023" to "GSSoC2024". | | `.github/ISSUE_TEMPLATE/feature.yml` | Updated program option from "GSSoC2023" to "GSSoC2024". | | `.github/advanced-issue-labeler.yml` | Updated label and keys from "gssoc23" to "gssoc24". | | `.github/workflows/add-label-issues.yml` | Updated label from "gssoc23" to "gssoc24" in the workflow description. | | `.github/workflows/add-label-prs.yml` | Updated label from "gssoc23" to "gssoc24" in the workflow script and log message. | ## Possibly related issues - **amupedia2021/amupedia-web#634**: The issue describes the need to update references from "GSSoC2023" to "GSSoC2024" in issue templates and advanced labeler configuration. - **amupedia2021/amupedia-web#627**: The issue highlights the outdated reference to "GSSoC2023" in the issue template, which needs to be updated to "GSSoC2024". > In the code's realm, where changes flow, > From '23 to '24, we go. > Labels shift, templates too, > Keeping everything fresh and new. > A rabbit's hop, a coder's dream, > Together, we make the perfect team. 🐇✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

github-actions[bot] commented 4 months ago

Thank you, @irfan-iiitr, for creating this pull request and contributing to GitHub-ReadMe! 💗

Our review team will thoroughly review the pull request and will reach out to you soon! 😇 Please make sure you have marked all the completed tasks as done. ✅ We appreciate your patience and contribution! 😀

irfan-iiitr commented 4 months ago

Please add appropriate level under the GSSoc label.

irfan-iiitr commented 3 months ago

@Ja3mamtora can you add the gssoc label and the level label in this. So that the score on the leaderboard of Gssoc increases. 🙏

amupedia2021 / amupedia-web

updated issue template and advanced labeler #644