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

Improved GitHub issue templates and enabled root folder in the VSCode workspace #1475

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

javiertoledo
Copy link
Member

No description provided.

@javiertoledo javiertoledo merged commit eee152c into main Oct 19, 2023
5 checks passed
@javiertoledo javiertoledo deleted the improved-github-issue-templates branch October 19, 2023 09:29
@what-the-diff
Copy link

what-the-diff bot commented Oct 19, 2023

PR Overview

  • Issue Template Update for Bug Reports
    Added an automatic label for bug reports, facilitating the process of identifying and tracking these types of issues.

  • Issue Template Title Revision for Documentation
    Revised the title for documentation issues to simplify and streamline identification.

  • Automatic Label for Feature Requests
    Implemented an automatic label for feature requests, aiding in the effortless categorization and monitoring of these requests.

  • New Template for Maintenance Tasks
    Introduced a new file "maintainance.md" to provide a structured approach when proposing maintenance tasks, enhancing project planning and execution.

  • Workspace Directory Structure Update
    Updated the directory structure in the code workspace, broadening its scope to include the root directory for easy access and navigation.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Oct 19, 2023

Apply Sweep Rules to your PR?

  • Apply: All docstrings and comments should be up to date.
  • Apply: Do not include large chunks of commented-out code.
  • Apply: Ensure that error logs use traceback during exceptions.
  • Apply: Remove debug logs and print statements from production code.
  • Apply: All the business logic in the 'src' folder for each package should have the corresponding unit tests in the 'test' folder in the same package.
  • Apply: Avoid 'any' types when possible.
  • Apply: If there's a simpler way to express a type, it should be used.

@ghost
Copy link

ghost commented Oct 19, 2023

👇 Click on the image for a new way to code review

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map legend

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.

1 participant