Set up code formatting and tests on github actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, formatter, or workflow details. Start by inspecting the repository structure, Python project configuration, and existing tests to identify the formatting and test commands. Done means a GitHub Actions workflow runs both checks successfully, with the selected commands and expected behavior documented.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 douglascdev/project_r
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
douglascdev/project_r#7 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
douglascdev/project_r#6 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
douglascdev/project_r#5 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
douglascdev/project_r#4 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
douglascdev/project_r#2 ·
All issues in douglascdev/project_r
Similar issues
-
Performance: deprecated DeviceEntry.config_entries access blocks the event loop for tens of secondsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tuya/tuya_cloud_ha_bridge#14 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
semantica-agi/semantica#1968 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
agent: ready area: submission priority: high type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dkritarth/scopewatch#213 ·
Maintainers usually reply within 1 day
-
Broken link in RELEASE.mdPossibly taken @Jah-yee claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
sphinx-contrib/httpdomain#143 ·
Maintainers usually reply within 1 day