google / google/yapf

Document best-practise for running yapf (in particular: for performance)

Open
#238 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
14k
Forks
904
PR merge metrics
No merged PRs in 30d

Description

The current documentation gives no opinion on how to efficiently run yapf.
Large, recursive re-runs are very slow.
Some opinionated documentation of how to optimise running would be very useful (perhaps calling a distinction between runs on CI and runs on developer machines).

This may be aided by profiling to determine how/where to optimise.
other ideas:
- tooling/config to detect git-changes and only re-yapf changed files
- a runner to split targets across CPUs

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.