Broken Link in Readme
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the README entry containing the libocr integration link and inspect the referenced Chainlink path. Replace the broken link with the correct destination, then verify that the README link resolves successfully.
Written by the indexing model from the issue text.
Description
- A link to libocr integration into actual chainlink node is broken
You may also be interested in libocr's integration into the actual Chainlink node.
- Dominant language
- Go
- Stars
- 82
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
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 smartcontractkit/libocr
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
smartcontractkit/libocr#127 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
smartcontractkit/libocr#87 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
smartcontractkit/libocr#35 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
smartcontractkit/libocr#34 ·
All issues in smartcontractkit/libocr
Similar issues
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·