|
11 | 11 |
|
12 | 12 | [](https://rubygems.org/gems/jekyll-theme-chirpy)
|
13 | 13 | [](https://github.com/cotes2020/jekyll-theme-chirpy/actions?query=branch%3Amaster+event%3Apush)
|
14 |
| - [](https://app.codacy.com/manual/cotes2020/jekyll-theme-chirpy?utm_source=github.com&utm_medium=referral&utm_content=cotes2020/jekyll-theme-chirpy&utm_campaign=Badge_Grade_Dashboard) |
| 14 | + [](https://www.codacy.com/gh/cotes2020/jekyll-theme-chirpy/dashboard?utm_source=github.com&utm_medium=referral&utm_content=cotes2020/jekyll-theme-chirpy&utm_campaign=Badge_Grade) |
15 | 15 | [](https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/LICENSE)
|
16 | 16 | [](https://996.icu)
|
17 | 17 |
|
@@ -74,6 +74,7 @@ $ bash tools/init.sh
|
74 | 74 | The above command will:
|
75 | 75 |
|
76 | 76 | 1. Removes some files or directories from your repository:
|
| 77 | + |
77 | 78 | - `.travis.yml`
|
78 | 79 | - files under `_posts`
|
79 | 80 | - folder `docs`
|
@@ -157,8 +158,7 @@ Now publish your Jekyll site by:
|
157 | 158 | 1. Push any commit to remote to trigger the GitHub Actions workflow. Once the build is complete and successful, a new remote branch named `gh-pages` will appear to store the built site files.
|
158 | 159 |
|
159 | 160 | 2. Browse to your repository on GitHub. Select the tab _Settings_, then click _Pages_ in the left navigation bar, and then in the section **Source** of _GitHub Pages_, select the `/(root)` directory of branch `gh-pages` as the [publishing source][pages-src]. Remember to click <kbd>Save</kbd> before leaving.
|
160 |
| - |
161 |
| -  |
| 161 | +  |
162 | 162 |
|
163 | 163 | 3. Visit your website at the address indicated by GitHub.
|
164 | 164 |
|
@@ -190,18 +190,18 @@ It depends on how you use the theme:
|
190 | 190 |
|
191 | 191 | - If you are using the theme gem (there will be `gem "jekyll-theme-chirpy"` in the `Gemfile`), editing the `Gemfile` and update the version number of the theme gem, for example:
|
192 | 192 |
|
193 |
| - ```diff |
194 |
| - - gem "jekyll-theme-chirpy", "~> 3.2", ">= 3.2.1" |
195 |
| - + gem "jekyll-theme-chirpy", "~> 3.3", ">= 3.3.0" |
196 |
| - ``` |
| 193 | + ```diff |
| 194 | + - gem "jekyll-theme-chirpy", "~> 3.2", ">= 3.2.1" |
| 195 | + + gem "jekyll-theme-chirpy", "~> 3.3", ">= 3.3.0" |
| 196 | + ``` |
197 | 197 |
|
198 |
| - And then execute the following command: |
| 198 | + And then execute the following command: |
199 | 199 |
|
200 |
| - ```console |
201 |
| - $ bundle update jekyll-theme-chirpy |
202 |
| - ``` |
| 200 | + ```console |
| 201 | + $ bundle update jekyll-theme-chirpy |
| 202 | + ``` |
203 | 203 |
|
204 |
| - As the version upgrades, the critical files (for details, see the [Startup Template][starter]) and configuration options will change. Please refer to the [Upgrade Guide](https://github.com/cotes2020/jekyll-theme-chirpy/wiki/Upgrade-Guide) to keep your repo's files in sync with the latest version of the theme. |
| 204 | + As the version upgrades, the critical files (for details, see the [Startup Template][starter]) and configuration options will change. Please refer to the [Upgrade Guide](https://github.com/cotes2020/jekyll-theme-chirpy/wiki/Upgrade-Guide) to keep your repo's files in sync with the latest version of the theme. |
205 | 205 |
|
206 | 206 | - If you forked from the source project (there will be `gemspec` in the `Gemfile` of your site), then merge the [latest upstream tags][latest-tag] into your Jekyll site to complete the upgrade.
|
207 | 207 | The merge is likely to conflict with your local modifications. Please be patient and careful to resolve these conflicts.
|
|
0 commit comments