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

updated issue template and advanced labeler #644

Merged
merged 1 commit into from
May 22, 2024

Conversation

irfan-iiitr
Copy link
Contributor

@irfan-iiitr irfan-iiitr commented May 20, 2024

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:

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

Checklist

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

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

Copy link

vercel bot commented May 20, 2024

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

Copy link

coderabbitai bot commented May 20, 2024

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

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
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

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

Copy link

@coderabbitai coderabbitai bot left a 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

Commits Files that changed from the base of the PR and between c5f45df and 694309f.
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

@irfan-iiitr
Copy link
Contributor Author

Please add appropriate level under the GSSoc label.

@Ja3mamtora Ja3mamtora merged commit 63c5ff4 into amupedia2021:develop May 22, 2024
4 checks passed
@irfan-iiitr
Copy link
Contributor Author

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

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.

2 participants