Skip to content

DEV: GitHub copilot instructions #831

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: develop
Choose a base branch
from

Conversation

Gui-FernandesBR
Copy link
Member

No description provided.

Copy link

codecov bot commented Jun 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.02%. Comparing base (4df0b38) to head (77f3e94).
Report is 26 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #831      +/-   ##
===========================================
+ Coverage    79.11%   80.02%   +0.90%     
===========================================
  Files           96       98       +2     
  Lines        11575    12004     +429     
===========================================
+ Hits          9158     9606     +448     
+ Misses        2417     2398      -19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Gui-FernandesBR Gui-FernandesBR force-pushed the dev/github-copilot-instructions branch from 20d49f7 to ab39b5d Compare June 20, 2025 00:00
@Gui-FernandesBR Gui-FernandesBR force-pushed the dev/github-copilot-instructions branch from ab39b5d to 77f3e94 Compare June 20, 2025 07:09
Comment on lines +21 to +22
- Use **Black formatter** for code formatting
- Line length: **88 characters** (Black's default)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I understand that ruff and black code formatting is very similar, but shouldn't we update this in favor of ruff? The same applies to the isort line.

@github-project-automation github-project-automation bot moved this from Backlog to Next Version in LibDev Roadmap Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next Version
Development

Successfully merging this pull request may close these issues.

2 participants