From 1a2530a780729baa3e5ae21f0cf6c9453aa9373f Mon Sep 17 00:00:00 2001
From: Jan Piotrowski <piotrowski+github@gmail.com>
Date: Thu, 2 Apr 2020 23:07:17 +0200
Subject: [PATCH] make providers headlines so they become linkable

(hopefully)
---
 errors/no-cache.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/errors/no-cache.md b/errors/no-cache.md
index 2056b7c88b56d..3951b1901b99a 100644
--- a/errors/no-cache.md
+++ b/errors/no-cache.md
@@ -1,12 +1,12 @@
 # No Cache Detected
 
-#### Why This Error Occurred
+### Why This Error Occurred
 
 A Next.js build was triggered in a continuous integration environment, but no cache was detected.
 
 This results in slower builds and can hurt Next.js' persistent caching of client-side bundles across builds.
 
-#### Possible Ways to Fix It
+### Possible Ways to Fix It
 
 > **Note**: If this is a new project, or being built for the first time in your CI, you can ignore this error.
 > However, you'll want to make sure it doesn't continue to happen and fix it if it does!
@@ -15,11 +15,11 @@ Configure Next.js' cache to be persisted across builds. Next.js stores its cache
 
 Storing this folder across builds varies by CI provider. We've provided a list of a few common providers below.
 
-**ZEIT Now**
+#### ZEIT Now
 
 Next.js caching is automatically configured for you. There's no action required on your part.
 
-**CircleCI**
+#### CircleCI
 
 Edit your `save_cache` step in `.circleci/config.yml` to include `.next/cache`:
 
@@ -34,7 +34,7 @@ steps:
 
 If you do not have a `save_cache` key, please follow CircleCI's [documentation on setting up build caching](https://circleci.com/docs/2.0/caching/).
 
-**Travis CI**
+#### Travis CI
 
 Add or merge the following into your `.travis.yml`:
 
@@ -46,7 +46,7 @@ cache:
     - .next/cache
 ```
 
-**GitLab CI**
+#### GitLab CI
 
 Add or merge the following into your `.gitlab-ci.yml`:
 
@@ -58,13 +58,13 @@ cache:
     - .next/cache/
 ```
 
-**Netlify CI**
+#### Netlify CI
 
 It is **not possible** to cache custom build files on Netlify. Please contact their support and request they support this behavior.
 
 You can investigate using a 3rd party solution (e.g. [`cache-me-outside`](https://github.com/DavidWells/cache-me-outside)) to manually cache the Next.js output.
 
-**AWS CodeBuild**
+#### AWS CodeBuild
 
 Add (or merge in) the following to your `buildspec.yml`:
 
@@ -75,7 +75,7 @@ cache:
     - '.next/cache/**/*' # Cache Next.js for faster application rebuilds
 ```
 
-**GitHub Actions**
+#### GitHub Actions
 
 Using GitHub's [actions/cache](https://github.com/actions/cache), add the following step in your workflow file:
 
@@ -86,7 +86,7 @@ with:
   key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}
 ```
 
-**Bitbucket Pipelines**
+#### Bitbucket Pipelines
 
 Add or merge the following into your `bitbucket-pipelines.yml` at the top level (same level as `pipelines`):