fix headers on public demo
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- jupyter-notebook
- Domain
- documentation
Research direction
Start by opening the public demo notebook and locating the headers shown in the issue image. Update the references so the demo identifies HealthyCode and explains its integration with PurlDB. Done means the public demo headers are accurate and the relationship between the two projects is clear.
Written by the indexing model from the issue text.
Description
current reference to PurlDB but would be good to update to HealthyCode and explain the integration with PurlDB
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 4
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 aboutcode-org/healthycode
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aboutcode-org/healthycode#23 ·
-
clean up repoMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aboutcode-org/healthycode#33 · 1 comment ·
-
healthycode: Document HealthyCode Deployment sizing parameters (Compute/Memory/Storage)Possibly taken @d4rshnn claimed this 10 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
aboutcode-org/healthycode#26 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
aboutcode-org/healthycode#25 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
aboutcode-org/healthycode#24 ·
All issues in aboutcode-org/healthycode
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
tronprotocol/tips#950 · 2 comments ·
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
crosspoint-reader/crosspoint-reader#4535 ·
Maintainers usually reply within 1 day
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bketelsen/pi-pocket-team#277 ·
Maintainers usually reply within 1 day