Skip to content

Conversation

@saibotk
Copy link
Member

@saibotk saibotk commented Apr 22, 2025

The security policy option is already shown through GitHub.

Additionally, the bug template needs to exist to be able to create an issue.
The link is automatically shown.

The template was taken from https://github.com/spatie/package-skeleton-laravel/blob/9ceafb99c72fe1ebca763c054667d0f102933675/.github/ISSUE_TEMPLATE/bug.yml

Summary by CodeRabbit

  • New Features

    • Introduced a standardized "Bug Report" issue template to streamline and improve bug reporting.
  • Chores

    • Updated issue template configuration by removing outdated contact links for reporting security issues and bugs.

The security policy option is already shown through GitHub.
Additionally, the bug template needs to exist to be able to create an issue. The link is automatically shown.
@saibotk saibotk self-assigned this Apr 22, 2025
@saibotk saibotk merged commit 6e18885 into main Apr 22, 2025
4 checks passed
@saibotk saibotk deleted the fix-issue-template branch April 22, 2025 19:08
@coderabbitai
Copy link

coderabbitai bot commented Apr 22, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A new bug report template was introduced in the GitHub issue templates directory to standardize and structure bug submissions. This template enforces required fields and uses dropdowns and text areas for comprehensive reporting. Additionally, the configuration file for issue templates was updated by removing contact links for reporting security issues and bugs, leaving only options for asking questions and requesting features.

Changes

File(s) Change Summary
.github/ISSUE_TEMPLATE/bug.yml Added a new structured bug report template with required fields and dropdowns for standardized bug submissions.
.github/ISSUE_TEMPLATE/config.yml Removed contact links for "Report a security issue" and "Report a bug"; left other contact links unchanged.

Poem

In the warren of code, a new form appears,
For bugs to be caught, with fewer lost years.
Dropdowns for systems, fields marked with care,
So every small glitch gets its fair share.
Old contact links gone, the path now refined—
A tidier burrow for all bugs to find!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6bb2bf4 and 6512d6b.

📒 Files selected for processing (2)
  • .github/ISSUE_TEMPLATE/bug.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/config.yml (0 hunks)

🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@studnitz
Copy link
Member

Thats sick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants