Skip to content

Add new bug report template and VSCode settings #1339

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aryan-dani
Copy link

🔄 Migrate Bug Report Template to GitHub Issue Forms

Summary

This PR replaces the Markdown-based bug report template with a structured YAML Issue Form to improve consistency and completeness of bug reports.

Changes

  • Removed: .github/ISSUE_TEMPLATE/bug_report.md
  • Added: .github/ISSUE_TEMPLATE/bug_report.yml
    • Includes fields for description, reproduction steps, expected vs actual behavior, and environment details
  • Added: .vscode/settings.json to provide Python environment hints for VS Code users

Benefits

  • Ensures standardized and detailed bug reports
  • Simplifies triaging and issue resolution
  • Aligns with current GitHub best practices

@facebook-github-bot
Copy link

Hi @aryan-dani!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@aryan-dani
Copy link
Author

Hi team,

I've signed the Facebook Contributor License Agreement (CLA) at https://code.facebook.com/cla, but the check still shows that I haven't signed it.

I’ve verified that the email used in my Git commits matches the one associated with my GitHub account and the CLA signature. Could you please help me resolve this issue or let me know if I need to take any additional steps?

Thank you!

Copy link
Author

@aryan-dani aryan-dani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self review Complete

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 29, 2025
@aryan-dani
Copy link
Author

Hi team! Just checking in on this PR. It aims to improve the bug reporting process by adopting GitHub's issue forms. I'm open to feedback or suggestions. Let me know if any changes are needed. Thanks!

@aryan-dani
Copy link
Author

Hi all, just following up on this PR again. I’d love to get your thoughts or any suggestions for improvement. If there’s anything blocking a review or if changes are needed, I’m happy to address them. Thanks for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants