Add flake8 bugbear

[Mews]

Created this pr in regards to #9

Changes

• Added flake8-bugbear to requirements-dev.txt so that it is installed when linting
• Added command in the linting.yml workflow to verify flake8 is picking up flake8-bugbear

Summary by CodeRabbit

• Chores
  • Updated linting workflow to include flake8-bugbear verification.
  • Added flake8-bugbear to development dependencies.

[coderabbitai]

Walkthrough

The recent updates enhance the project's linting workflow by integrating flake8-bugbear for more robust code analysis. The .github/workflows/linting.yml file now includes a step to verify flake8 is using flake8-bugbear before running the linting command. Additionally, flake8-bugbear has been added to requirements-dev.txt to ensure it is installed with other development dependencies.

Changes

Files	Change Summary
.github/workflows/linting.yml	Added a verification step for flake8 to ensure it picks up flake8-bugbear before running linting.
requirements-dev.txt	Included flake8-bugbear in the list of development dependencies.

Poem

In the land of code, where bugs do hide,
A new tool joins, with eyes open wide. 🐇
Flake8-bugbear, now in our kin,
To catch the errors, where they begin.
Linting stronger, our code refined,
A brighter future, intertwined. 🌟

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[Seluj78]

One little tip for your next PR that might come in handy:

https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

.github/workflows/linting.yml (1)

34-34: Ensure the lint command is correctly configured. Consider adding a comment explaining why these specific directories are excluded from linting for clarity and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2cb807e and 41a6362.

Files selected for processing (2)

• .github/workflows/linting.yml (1 hunks)
• requirements-dev.txt (1 hunks)

Files skipped from review due to trivial changes (1)

• requirements-dev.txt

Additional comments not posted (1)

.github/workflows/linting.yml (1)

33-33: Good addition to verify the installation of flake8-bugbear.

[Seluj78]

Congratulations on your first PR on this repository ! 🙌

[Seluj78]

And you code is now released here ! 🙌 🔥 https://github.com/Seluj78/flask-utils/releases/tag/v0.4.0

[Mews]

Thanks for this opportunity :)
Hopefully this will be the first of many pr's I open on github :P