Address repo-review comments
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, testing, tooling
Research direction
Start by reviewing pyproject.toml and .pre-commit-config.yaml against the failed repo-review checks, then inspect whether the repository has a tests folder and task-runner configuration. Confirm the relevant pytest, mypy, Ruff, and pre-commit requirements before making changes. Done means the listed PY, PP, PC, MY, and RF checks pass.
Written by the indexing model from the issue text.
Description
General
- Detected build backend:
setuptools.build_meta - Detected license(s): Apache Software License
| ? | Name | Description |
|---|---|---|
| ❌ | PY005 |
Has tests folder
Projects must have a folder called |
| ❌ | PY007 |
Supports an easy task runner (nox or tox)
Projects must have a |
PyProject
| ? | Name | Description |
|---|---|---|
| ❌ | PP301 |
Has pytest in pyproject
Must have a |
Pre-commit
| ? | Name | Description |
|---|---|---|
| ❌ | PC111 |
Uses blacken-docs
Must have |
| ❌ | PC140 |
Uses mypy
Must have |
| ❌ | PC160 |
Uses codespell
Must have |
| ❌ | PC180 |
Uses prettier
Must have |
| ❌ | PC901 |
Custom pre-commit CI message
Should have something like this in
|
MyPy
| ? | Name | Description |
|---|---|---|
| ❌ | MY101 |
MyPy strict mode
Must have
|
| ❌ | MY102 |
MyPy show_error_codes deprecated
Must not have |
Ruff
| ? | Name | Description |
|---|---|---|
| ❌ | RF101 |
Bugbear must be selected
Must select the flake8-bugbear
|
| ❌ | RF202 |
Use (new) lint config section
|
- Dominant language
- Python
- Stars
- 181
- Forks
- 49
- Avg merge
- 43m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xarray-contrib/cf-xarray
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
xarray-contrib/cf-xarray#623 ·
-
Consider adding opt-in support for circular axes when calling `bounds_to_vertices` (related to #594) Open
Difficulty 5/5 Over a week Newbie friendliness 38/100
xarray-contrib/cf-xarray#596 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
xarray-contrib/cf-xarray#570 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
xarray-contrib/cf-xarray#568 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
xarray-contrib/cf-xarray#566 · 2 comments ·
All issues in xarray-contrib/cf-xarray
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100