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.
...
- 10 commits
- 21 files changed
- 3 contributors
Commits on Sep 28, 2017
-
Recommend pinning prettier version (#2920)
* Recommend pinning prettier version * Change from -E to --exact/--save-exact
-
-
Update postcss-values-parser (#2928)
My PR has been merged and released to npm, so no need to depend on my fork anymore.
Commits on Sep 29, 2017
-
Fix Travis production builds (#2933)
* Fix Travis production builds * Fix Travis production builds, attempt 2 * Remove `allow_failures` in .travis.yml The reason we allowed the production builds to fail in the first place: ❯ git show 532ac0d commit 532ac0d Author: Joseph Frazier <[email protected]> Date: 2017-06-17 19:37:51 -0400 Build/test dist/ on Travis (#2176) This helps us keep track of whether or not the dist/ build actually works (see #2174). Note that the dist/ jobs are allowed to fail, and do not affect overall build time, so they shouldn't slow anything down (see https://blog.travis-ci.com/2013-11-27-fast-finishing-builds/). However, as we discovered in #2933 requiring the production builds to succeed only adds about 1 minute of build time, so it is not worth the risk of missing that the production builds fail. -
Commits on Sep 30, 2017
Loading
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 1.7.2...1.7.3