winglang/wing

PR linter

Open

#482 opened on 2022幎11月7日

GitHub で芋る
 (4 comments) (0 reactions) (0 assignees)TypeScript (214 forks)github user discovery
good first issue👷‍♀ contributor-experience

Repository metrics

Stars
 (5,385 stars)
PR merge metrics
 (30d に merged PR はありたせん)

説明

PRs that change certain things should require new/changed example wing files to ensure coverage is available for the various tests that consume those files.

Feature Spec

Suggested projects to require test cases:

  • tree-sitter-wing
  • wingc (maybe only certain files, like the parser/typechecker/jsify)

Use Cases

Testing is often easy to forget, but for such foundational changes, we should nudge contributors to add bare minimum testing.

Implementation Notes

I think it would be interesting to look into generic tooling to support PR lints. e.g. https://danger.systems/js/

Also note we use mergify, which can also help

Component

  • Development Environment
  • Contributor Experience

コントリビュヌタヌガむド