-
Notifications
You must be signed in to change notification settings - Fork 173
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
updated issue template and advanced labeler #644
updated issue template and advanced labeler #644
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughWalkthroughThe 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
Possibly related issues
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
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! 😇 |
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.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (6)
- .github/ISSUE_TEMPLATE/bug_report.yml (1 hunks)
- .github/ISSUE_TEMPLATE/doc.yml (1 hunks)
- .github/ISSUE_TEMPLATE/feature.yml (1 hunks)
- .github/advanced-issue-labeler.yml (1 hunks)
- .github/workflows/add-label-issues.yml (1 hunks)
- .github/workflows/add-label-prs.yml (2 hunks)
Files skipped from review due to trivial changes (5)
- .github/ISSUE_TEMPLATE/bug_report.yml
- .github/ISSUE_TEMPLATE/doc.yml
- .github/ISSUE_TEMPLATE/feature.yml
- .github/advanced-issue-labeler.yml
- .github/workflows/add-label-prs.yml
Additional comments not posted (1)
.github/workflows/add-label-issues.yml (1)
27-27
: Updated step name to reflect the new label for 2024.Verification successful
The 'gssoc24' label exists in the repository, confirming that the workflow step to add this label is valid.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the 'gssoc24' label exists in the repository labels. # Test: Fetch repository labels and check for 'gssoc24'. Expect: 'gssoc24' should be listed. gh api repos/:owner/:repo/labels | jq '.[] | select(.name == "gssoc24")'Length of output: 354
Please add appropriate level under the GSSoc label. |
@Ja3mamtora can you add the gssoc label and the level label in this. |
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:
Checklist
Please check all applicable boxes and provide any additional information if needed.
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.