Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 5 commits
- 19 files changed
- 4 contributors
Commits on Sep 29, 2018
Commits on Oct 29, 2018
-
feat: Add support for partially staged files (#75)
Introduces support for partially staged files with the following algorithm: 1. Before running linters, check if there are partially stated files (i.e. both with changes in commit index and the working copy) 2. Stash and remove from the working copy all files that aren't in the commit index 3. Execute commands (linters and formatters) on these files 4. Add formatters changes to index (separate task in the config) 5. Restore the stashed working copy state if all linters exit with zero code (i.e. success). If there are errors running linters, restore stashed working copy. 6. Compare new commit index and working copy and apply as many formatting changes to working copy as possible. If there are conflicting hunks, drop formatter's changes. User modifications that were stashed should always take precedence over formatters. Closes #62 BREAKING CHANGE: Node >= 8.6 is required
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.3.0...v8.0.0