Skip to content
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.
base repository: gatsbyjs/gatsby
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: [email protected]
Choose a base ref
...
head repository: gatsbyjs/gatsby
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: [email protected]
Choose a head ref
  • 16 commits
  • 46 files changed
  • 11 contributors

Commits on Nov 20, 2018

  1. docs: fix Create a Gatsby site link (#10051) 

    In the [Set Up Your Development Environment](https://www.gatsbyjs.org/tutorial/part-zero/) page, the link with label "Create a Gatsby site" (sidebar) refers to #create-a-site instead of #create-a-gatsby-site.
    @Rahmon @pieh
    Rahmon authored and pieh committed Nov 20, 2018
    Copy the full SHA
    905e966 View commit details

Commits on Nov 21, 2018

  1. chore(www): update gatsby and gatsby-plugin-offline (#10054) 

    just to trigger dep reinstallation for our build runner
    @pieh @KyleAMathews
    pieh authored and KyleAMathews committed Nov 21, 2018
    Copy the full SHA
    59ee6d3 View commit details

  2. added a new website (#10053) 

    added a new website to showcase

<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
    @prasadseth @DSchau
    prasadseth authored and DSchau committed Nov 21, 2018
    Copy the full SHA
    66b2012 View commit details

  3. Fix typo in README.md (#10056)

    @czakarian @DSchau
    czakarian authored and DSchau committed Nov 21, 2018
    Copy the full SHA
    8d07c2f View commit details

  4. fix(gatsby-plugin-sharp): use actions provided, don't assume Gatsby m… 

    …odule location. (#9986)

The gatsby module resolve by require might not be the gatsby module that is executing. This can occur in mono-repo configurations.

This will prevent the Redux store from receiving the job actions and the bootstrap process will complete without waiting for all images to be processed. This can cause the build to finish without all images being generated.

Fixes #9984.
    @martin-css @pieh
    martin-css authored and pieh committed Nov 21, 2018
    Copy the full SHA
    54f6a85 View commit details

  5. chore(release): Publish 

     - [email protected]
 - [email protected]
 - [email protected]
    @pieh
    pieh committed Nov 21, 2018
    Copy the full SHA
    656b006 View commit details

  6. Adding Tandem website to sites list (#10065) 

    Adds https://tandem.co.uk to sites list
    @alechill @pieh
    alechill authored and pieh committed Nov 21, 2018
    Copy the full SHA
    3ae518c View commit details

  7. chore(gatsby): remove unused nyc dependency (#10063)

    @alexandernanberg @pieh
    alexandernanberg authored and pieh committed Nov 21, 2018
    Copy the full SHA
    ec2cef3 View commit details

  8. fix(prettier): ignore coverage directory (#10064)

    @alexandernanberg @pieh
    alexandernanberg authored and pieh committed Nov 21, 2018
    Copy the full SHA
    cadf9f3 View commit details

  9. feat(gatsby): warn user about incompatible plugins (#10034) 

    Closes: #7143 #9731
<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
    @oorestisime @pieh
    oorestisime authored and pieh committed Nov 21, 2018
    Copy the full SHA
    8421707 View commit details

  10. chore(release): Publish 

     - [email protected]
    @pieh
    pieh committed Nov 21, 2018
    Copy the full SHA
    3ed9735 View commit details

  11. feat(gatsby-remark-images): make images blur up (#7800) 

    BREAKING CHANGE: html markup has been changed, high resolution image (img.gatsby-resp-image-image) is no longer nested inside span with low resolution placeholder  (span.gatsby-resp-image-wrapper) - it's sibling of that span now. This might affect any custom styling that is applied to inline images
    @jamesadarich @pieh
    jamesadarich authored and pieh committed Nov 21, 2018
    Copy the full SHA
    5a5254e View commit details

  12. chore(release): Publish 

     - [email protected]
    @pieh
    pieh committed Nov 21, 2018
    Copy the full SHA
    351aaa3 View commit details

  13. docs(gatsby-plugin-offline): Add instructions for removing service wo… 

    …rker (#10075)

Related to #9913
    @jgierer12 @pieh
    jgierer12 authored and pieh committed Nov 21, 2018
    Copy the full SHA
    73167e3 View commit details

  14. feat(gatsby-plugin-manifest): don't output theme-color meta tag if … 

    …it's not defiened (#10069)

Not really sure how I go about submitting a PR here. This addition references issue #9977

Any guidance would be greatly appreciated.
    @DZuz14 @pieh
    DZuz14 authored and pieh committed Nov 21, 2018
    Copy the full SHA
    7802470 View commit details

  15. chore(release): Publish 

     - [email protected]
 - [email protected]
 - [email protected]
    @pieh
    pieh committed Nov 21, 2018
    Copy the full SHA
    4d246c2 View commit details
Loading