lingochamp / lingochamp/okcheck

老项目第一次全量检查失败,是不是就无法进行增量检查了?

Open
#14 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
304
Forks
29
PR merge metrics
No merged PRs in 30d

Description

因为是老项目,所以全量检查有很多问题,那么是不是这个库就不适用了?
![image](https://user-images.githubusercontent.com/18431596/64665965-2e103b80-d487-11e9-861c-0342b7db3eee.png)
![image](https://user-images.githubusercontent.com/18431596/64665975-3799a380-d487-11e9-9a47-ad16e03d6588.png)

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

No file, test, or entry point is named. Start by reproducing the reported full-scan failure in an old project and trace how a failed full scan affects incremental-scan state; done means determining whether incremental checks remain usable and documenting the relevant failure condition.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.