yaml / yaml/libyaml

https://github.com/yaml/libyaml/issues/321#issuecomment-3703927906

Open
#322 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.2k
Forks
370
PR merge metrics
No merged PRs in 30d

Description

tpoo_jap.pdf

Originally posted by @soekhantpaing130-dev in #321

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #321 and the attached tpoo_jap.pdf; this issue contains no libyaml behavior, file, or test to investigate. Confirm with maintainers whether it is a valid report; no completion criteria are provided.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
1/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.