blocks|key|153041|text|参加聚会有点晚了，但我刚刚遇到这个问题，上面的任何一个都没有涵盖我的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153042|具体来说，我的问题如下：|153043|153044|我创建了一个具有自定义域的github.pages站点。|unordered-list-item|153045|我正在将提交推送到正确的GitHub分支，但看不到github.pages站点上的更新。|153046|153047|解决方案：这个问题原来是我的浏览器缓存页面造成的(尽管我禁用了页面缓存)。为了解决这个问题，我只清除了过去一个小时的缓存数据，这立即就起作用了。|offset|length|style|BOLD|153048|要清除Chrome中的缓存数据，请进入Chrome菜单，然后选择More+Tools+>+Clear+Browsing+Data。|CODE|153049|我不知道是什么导致了缓存，这个github.pages/自定义域的组合是唯一导致我缓存的原因。|153050|entityMap^0|0|0|0|0|0|0|0|5|0|W|W|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|11|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@$M|14|N|15|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|16|8|@$M|17|N|18|O|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|W|$]]

A bit late to the party but I just had this issue and my solution isn't covered by any of the above.

Specifically my issue was the following:

<ul>
<li>I had created a github.pages site with a custom domain.</li>
<li>I was pushing commits to the correct GitHub branch but not seeing the updates on the github.pages site.</li>
</ul>

Solution:
The issue turned out to be my browser caching the page (despite my having page caching disabled). To fix it I just cleared my cached data from the past hour and that worked instantly.

To clear the cache data in Chrome go to the Chrome menu then <code>More Tools &gt; Clear Browsing Data</code>.

I don't know what caused the caching, this github.pages/custom domain combo is the only thing that has ever caused it for me.

blocks|key|151518|text|有时这种情况也会发生在我身上:在创建并推送gh-pages之后，GitHub+Pages页面丢失或没有更新。即使我向分支提交更多更改并再次推送，它也不会在GitHub页面上更新。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|151519|如果我没记错的话，我通过从服务器上删除分支并再次推送它来解决这个问题：|151520|git+push+origin+:gh-pages
git+push+origin+gh-pages|code-block|syntax|javascript|151521|我可能不得不添加一些虚拟提交，然后再次推送以触发更新，我不太记得了……|151522|entityMap^0|L|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

Sometimes this happens to me too: after creating and pushing the <code>gh-pages</code>, the GitHub Pages page is missing or not getting updated. Even if I commit more changes to the branch and push it again, it won't update on GitHub pages.

If I remember correctly, I solve this by deleting the branch from the server and pushing it again:

<pre><code>git push origin :gh-pages
git push origin gh-pages
</code></pre>

I might have to add some dummy commits and push again to trigger the update, I don't remember exactly...

blocks|key|151595|text|我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151596|您可以尝试进入设置页面。|151597|我进入项目设置页面(.../+settings+/+pages+)，发现Github页面给我一些消息“某些语法错误”，我修复了它，然后就好了。|151598|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I fixed this problem.
you can try to go to the setting page.
I go into the project settings page (.../settings/pages) ,and found Github pages give me some message &quot;some syntax error&quot;, I fixed it, and ok.

blocks|key|151550|text|我也有同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151551|问题是我的网站是从gh-pages分支发布的，但我将我最近的更改推到了master分支。|151552|检查Github是从哪个分支发布您的网站。在您的存储库中，单击Settings，向下滚动页面，应该会有一个框，您可以在其中更改发布分支。|151553|它应该看起来像这样：|151554|📷|atomic|offset|length|151555|​|151556|更多信息请访问here|151557|另外，如果您使用的是自定义域名，请确保您的CNAME文件是最新的。|151558|希望这能有所帮助！|151559|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cb45ec5123b4589daf6348b11c917d2f.png|imageAlt|1|LINK|MUTABLE|url|https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/^0|0|0|0|0|0|1|0|0|0|7|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1C|8|@]|9|@$K|1D|L|1E|1|1F]]|A|$]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1H|8|@]|9|@$K|1I|L|1J|1|1K]]|A|$]]|$1|Q|3|R|5|6|7|1L|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1M|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]|13|$5|14|Y|15|A|$16|17]]]]

I had the same issue. 

The problem was that my website was publishing from the gh-pages branch, but I was pushing my recent changes to the master branch. 

Check which branch Github is publishing your website from. In your repository, click on Settings, scroll down the page and there should be a box where you you can change the publishing branch. 

It should look like this:
<img src="https://i.stack.imgur.com/Geu2j.png" alt="">

More info is <a href="https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/" rel="noreferrer">here</a>

Also if you are using a custom domain name, make sure your CNAME file is up to date.

Hope that helps!

blocks|key|2735642|text|尝试像这样推送空提交|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2735643|$+git+commit+--allow-empty+-m+"Empty+commit"|code-block|syntax|javascript|2735644|每次都对我很有吸引力。|2735645|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Try to push empty commit like this

<pre><code>$ git commit --allow-empty -m "Empty commit"
</code></pre>

Works like a charm for me every time.

blocks|key|151588|text|当文件名包含单词“供应商”时遇到此问题。例如：vendor.bundle.20d44fcf5147c6ed68a3.js|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|151589|在存储库的根目录中添加名为.nojekyll的空文件修复了此问题。|151590|151591|+Jekyll现在默认情况下会忽略vendor和node_modules目录https://github.com/blog/2277-what-s-new-in-github-pages-with-jekyll-3-3|blockquote|151592|151593|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/blog/2277-what-s-new-in-github-pages-with-jekyll-3-3^0|N|11|0|D|9|0|0|H|6|O|C|12|1Z|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|L|3|-4|5|6|7|19|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Experienced this problem when a filename contained the word "vendor" ex.:<code>vendor.bundle.20d44fcf5147c6ed68a3.js</code>

Adding an empty file named <code>.nojekyll</code> in the root of the repository fixed the issue.

<blockquote>
 Jekyll now ignores the <code>vendor</code> and <code>node_modules</code> directories by default
 <a href="https://github.com/blog/2277-what-s-new-in-github-pages-with-jekyll-3-3" rel="noreferrer">https://github.com/blog/2277-what-s-new-in-github-pages-with-jekyll-3-3</a>
</blockquote>

blocks|key|151600|text|要解决这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151601|151602|将当前Github+Pages分支切换到其他分支，然后单击Save+|ordered-list-item|offset|length|style|CODE|151603|切换回所需的Github+Pages分支，然后单击Github|151604|151605|这将强制Github更新您的更改。|151606|entityMap^0|0|0|T|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

To solve this issue 

<ol>
<li>Switch your current Github Pages branch to some other branch and click
on <code>Save</code> </li>
<li>Switch back to your desirable Github Pages branch and click on <code>Save</code>.</li>
</ol>

This will force Github to update your changes.

blocks|key|2735797|text|我是一个新手，请允许我含泪回答。请转到存储库的设置，向下滚动到|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2735798|📷|atomic|2735799|检查您当前的网页是否有问题。如果有问题，您的网站将不会被更新。我认为这是一种保护机制或别的什么。|2735800|今天早上我删除并移动了存储库中的一些文件，我已经更新了很多次，它仍然保留在以前的版本中，即使我检查了index.html确实更新了。后来，我关闭了整个存储库，并启动了一个新的存储库，一个接一个地插入项目，但仍然遇到了问题。我试过像gh-pages这样的新分支，我认为对于像我这样的初学者来说，是不必要的。后来我检查了我的设置，发现了通知，我删除了有问题的文件，它立即工作。如果我知道这个问题，我就不会愚蠢到永远关闭它。我怀念我的旧唱片。我猜每一堂课都是要付出代价的，Github也不例外。|2735801|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5bf35ed82e73a23c77f520da45e39440.png|imageAlt^0|N|8|0|0|1|0|1|0|0|0|8|E|G|0|42|2Q|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|I|3|J|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T|U|-4]]]]

I am a novice and please allow me to answer with tears. Please go to settings at your repository, scroll down to <a href="https://i.stack.imgur.com/JJ2tj.png" rel="noreferrer"><img src="https://i.stack.imgur.com/JJ2tj.png" alt="enter image description here"></a> to check WHETHER THERE IS A PROBLEM with your current webpage. If there is a problem, your site WILL NOT BE UPDATED. I think it's a protection mechanism or something.

This morning I deleted and moved some of the files in repository, I have updated many times and it still remains on previous version, even I checked the index.html has indeed updated. Later I shut down the whole repository and started new one, inserting items one by one, but still met the problem. I tried new branch like gh-pages, I think it is not necessary for a beginner like me. Later I checked my settings and found the notification, I deleted the problematic files and it worked instantly. Were I knew the problem I would not have been so stupid to shut down it forever. I miss my old git records. Guess every lesson takes a price, Github is no exception.

blocks|key|154321|text|我试过Janos'+answer，但它对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|154322|我对我的index.html文件做了一个小改动(一些无关紧要的事情)，并再次推送到gh-pages分支。我试着在不同的浏览器中打开页面，它工作了。我原来的浏览器也更新了页面，尽管我不认为这是浏览器缓存的问题。|style|CODE|154323|我在本地使用gh-pages重新设置了master的基数，并将其推送到本地，不确定这是否会有什么不同。|154324|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/641955/janos^0|3|6|0|0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I tried <a href="https://stackoverflow.com/users/641955/janos">Janos'</a> answer but it didn't work for me.

I made a slight change to my <code>index.html</code> file (something insignificant) and pushed to the gh-pages branch again. I tried opening the page in a different browser and it worked. My original browser updated the page too although I don't think it's a browser cache issue.

I rebased master with gh-pages locally and pushed that as well, not sure if that makes any difference.

blocks|key|2735624|text|尝试禁用GitHub页面，并在几分钟后启用它。我试过了。这是可行的。但是更新和重新启用GitHub页面需要一些时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2735625|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try to disable GitHub pages, and enable it after a few minutes. I tried. This works. But It takes some time to update and re-enable GitHub Pages.

blocks|key|150452|text|我最近遇到了一个问题，我的github页面托管站点无法从master中的旧分支推送进行更新。我可以通过转到domain.com.查看新的更改(末尾的点很重要)，而且硬刷新将显示新的更改，但如果定期刷新，它也会显示旧站点和旧JS文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|150453|我的问题似乎只出现在Chrome上，这就是我开发网站的地方。为了充分披露，旧的更改是在React中并托管在Netlify中的。我试图推送和显示的新更改是托管在github页面中的静态文件。|150454|修复(在Chrome中)：+devtools+>应用程序>清除站点数据(按钮)。|150455|entityMap^0|S|6|1H|B|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

I recently had an issue where my github pages hosted site wasn't updating from an old branch push in <code>master</code>. I was able to see the new changes by going to <code>domain.com.</code> (the dot at the end is important), and also hard refreshing would show the new changes, but with a regular refresh, it would show the old site and the old JS files too.

My problem seemed to only be in Chrome, which is where I was developing the site. For full disclosure, the old changes were in React and hosted in Netlify. The new changes that I was trying to get to push and display were static files hosted in github pages.

THE FIX (in Chrome): devtools > Application > clear site data (button).

blocks|key|2735627|text|我遇到了同样的问题，我的存储库中的所有内容都是最新的，但它仍然没有加载到我的github页面，所以没有做任何进一步的更改，我尝试添加、提交和拉入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2735628|我用另一个git+commit修复了它，然后git再次拉出。现在，更改已加载到我的git中。|2735629|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem everything is up to date in my repository but it still wasn't loading to my github page, so without making any further changes, I tried to add, commit and pull.

I fixed it with another git commit, and git pull again.
Now the changes are loaded to my git.

blocks|key|153180|text|此问题是由于浏览器缓存页面而导致的。在隐身模式下打开git+link。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|153181|entityMap|0|LINK|mutability|MUTABLE|url|https://username.github.io/folderName/folder/file.ext^0|U|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The issue is being caused because of the browser caching the page. Open the git <a href="https://username.github.io/folderName/folder/file.ext" rel="nofollow noreferrer">link</a> in incognito mode.

blocks|key|151763|text|此答案适用于使用create-react-app.创建应用程序的用户|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|151764|我花了几天的时间终于找到了react-gh-pages不更新的答案。我希望下面的答案对我有帮助。这是我研究过的多个答案的组合：|151765|最主要也是最常见的原因是浏览器的缓存功能。为了在每次渲染index.html时禁用它，|151766|151767|将此代码段添加到公用文件夹下的index.html文件中。|ordered-list-item|151768|151769|​|151770|<meta+http-equiv='cache-control'+content='no-cache'>+
<meta+http-equiv='expires'+content='0'>+
<meta+http-equiv='pragma'+content='no-cache'>|code-block|syntax|javascript|151771|151772|151773|将所有新更改推送到主分支或主分支(而不是原始页面)。|151774|至此，您的主分支已更新。|151775|现在运行：git+push+origin+:gh-pages。这将删除gh-pages分支。|CODE|151776|运行：npm+run+deploy。这将构建你的应用程序，并使用更新的内容重新创建gh-pages分支。|151777|现在转到应用程序回购页面右上角的设置部分。向下滚动到底部。在Github+Pages部分的源代码下，有一个分支部分。将其更改为您的主分支或主分支。保持根文件夹的原样。|151778|转到您的站点，您将看到一个自述文件。这可能需要一些时间。大约一分钟后，将分支改回gh-pages。一分钟后访问你的网站，现在应该已经更新了。|151779|151780|我希望这能帮到你!请在评论区让我知道它是否也适用于您，干杯！|151781|entityMap^0|8|H|0|0|0|0|0|0|0|0|0|0|0|0|5|P|0|3|E|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1I|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1J|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1L|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1N|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1O|8|@]|D|@]|E|$T|U]]|$1|V|3|P|5|6|7|1P|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|X|3|Y|5|M|7|1R|8|@]|D|@]|E|$]]|$1|Z|3|10|5|M|7|1S|8|@]|D|@]|E|$]]|$1|11|3|12|5|M|7|1T|8|@$9|1U|A|1V|B|13]]|D|@]|E|$]]|$1|14|3|15|5|M|7|1W|8|@$9|1X|A|1Y|B|13]]|D|@]|E|$]]|$1|16|3|17|5|M|7|1Z|8|@]|D|@]|E|$]]|$1|18|3|19|5|M|7|20|8|@]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|21|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|22|8|@]|D|@]|E|$]]|$1|1D|3|-4|5|6|7|23|8|@]|D|@]|E|$]]]|1E|$]]

This answer is for those who have created their app with create-react-app.
It took me days to finally find the answer for react-gh-pages not updating. I hope the following answer helps as it did for me. It is a combination of multiple answers that I have researched over:
The main and most common reason is your browsers caching feature. In order to disable it for every rendering of your index.html,
<ol>
<li>Add this snippet in your index.html file under the public folder.</li>
</ol>
<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>&lt;meta http-equiv='cache-control' content='no-cache'&gt; 
&lt;meta http-equiv='expires' content='0'&gt; 
&lt;meta http-equiv='pragma' content='no-cache'&gt;</code></pre>
</div>
</div>

<ol start="2">
<li>Push any new changes to the master or main branch(not to the origin gh-pages).</li>
<li>By now your master branch is updated.</li>
<li>Now run: <code>git push origin :gh-pages</code>. This will delete the gh-pages branch.</li>
<li>Run: <code>npm run deploy</code>. This will build build your app and re-create gh-pages branch
with updated content.</li>
<li>Now go the settings section on the top-right side of your app repo page. Scroll down to the bottom. Under Github Pages section, under source, there is branch section. Change that to your master branch or main. Keep the root folder as it is.</li>
<li>Go to your site and you will see a Readme file. It may take some time. After a minute or so change the branch back to gh-pages. After a minute visit your site and it should be updated by now.</li>
</ol>
I hope this helps! Let me know if it worked for you as well in the comment section, cheers!

blocks|key|2948725|text|如果您的GitHub页面存储库是私有的，并且您最近已降级为免费GitHub，则这可能适用于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2948726|免费订阅，GitHub+|2948727|，不支持私有存储库的GitHub+Pages站点。在一月份引入免费私有存储库后，我们发现连接到私有存储库的有限数量的站点被错误地保留为活动的。如果你想继续更新这个网站，你可以公开它的存储库或者升级到GitHub专业版。您也可以在下面取消发布它。此站点正在使用自定义CNAME:在取消发布此站点之前保护您的域名。|blockquote|2948728|2948729|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If your GitHub pages repo is private AND you have recently downgraded to GitHub Free, this might apply:
<blockquote>
Your subscription, GitHub Free, does not support GitHub Pages sites
for private repositories. After we introduced free private
repositories in January, we found a limited number of sites connected
to private repositories were mistakenly left active. If you’d like to
keep updating this site, you can make its repository public or upgrade
to GitHub Pro. You can also unpublish it below. This site is using a
custom CNAME: Secure your domain name before unpublishing this site.
</blockquote>

blocks|key|2948236|text|以下是对我有效的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2948237|第一步(更新你的master)：|2948238|git+add+.+

git+status++++++++++++++++#+to+see+the+changes+to+be+committed

git+commit+-m+"comments"

git+push+origin+master|code-block|syntax|javascript|2948239|第二步(更新gh-pages)：|2948240|git-checkout+gh-pages+++++#+going+to+the+gh-pages+branch

git+rebase+master+++++++++#+sync+gh-pages+with+master+

git+push+origin+gh-pages++#+commit+changes+to+gh-pages

git+checkout+master+++++++#+return+to+the+master+|2948241|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Here is what worked for me: 

First Step (update your master): 

<pre class="lang-none prettyprint-override"><code>git add . 

git status # to see the changes to be committed

git commit -m "comments"

git push origin master
</code></pre>

Second Step (Update gh-pages):

<pre class="lang-none prettyprint-override"><code>git-checkout gh-pages # going to the gh-pages branch

git rebase master # sync gh-pages with master 

git push origin gh-pages # commit changes to gh-pages

git checkout master # return to the master 
</code></pre>

blocks|key|151622|text|在脚本中进行更改后，转到commit+changes部分。在那里你会发现一个输入框和一个文本区。正如你们都知道的，填满这些盒子并不是强制性的，但它们存在是有原因的。因此，下次单击commit+changes按钮之前，请尝试>>，确保您在第一个输入框中写入了某些内容(您可以将文本区域保留为空)，并且您编写的内容与上次提交同一文件时编写的内容不同。通过这种方式，github将能够区分当前脚本和更新的脚本，并且更改应该几乎立即反映出来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151623|希望这能有所帮助。|151624|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

After making changes in your script, go down to the commit changes section. There you'll find one input box and one text-area. As you all know filling those boxes is not mandatory, but they are there for a reason. So, next time before clicking on the commit changes button give this a try >> make sure that you write something in the first input box (you can leave the text-area empty), and what you write is different from what you wrote for your last commit for the same file. In this way github will be able to distinguish between the current script and the updated one, and the change should be reflected almost instantly.

Hope that helps.

blocks|key|153079|text|最简单的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153080|153081|设置->分支->选择"gh-pages“->更新。|blockquote|153082|153083|153084|Take+mine+as+example|offset|length|153085|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/7NiwD.png^0|0|0|0|0|0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$J|Z|K|10|1|11]]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

The easiest way:

<blockquote>
 Settings -> Braches -> choose "gh-pages" -> UPDATE.
</blockquote>

<a href="https://i.stack.imgur.com/7NiwD.png" rel="nofollow noreferrer">Take mine as example</a>

blocks|key|153172|text|以防这对其他人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153173|对我来说，问题是分支中的内容正在更新，但文件名没有更改，因此浏览器正在检索缓存的内容。|153174|我在angular-cli-ghpages中使用Angular+CLI。将配置设置为production会在构建中的每个文件后附加散列，从而强制浏览器检索新内容。|offset|length|153175|示例部署脚本：|153176|ng+build+--configuration=production+--base-href+\"<repo-name>\"+&&+ngh|code-block|syntax|javascript|153177|如果不需要生产构建，还可以在angular.json的其他构建配置中指定输出散列|style|CODE|153178|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/angular-cli-ghpages^0|0|0|2|J|0|0|0|0|E|C|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@$F|13|G|14|1|15]]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|18|8|@$F|19|G|1A|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

In case this helps someone else...

For me the issue was the content in the branch was being updated, but the filenames did not change, so browser was retrieving cached content.

I'm using Angular CLI with <a href="https://www.npmjs.com/package/angular-cli-ghpages" rel="nofollow noreferrer">angular-cli-ghpages</a>. Setting the configuration to production appends hashes after each file in the build forcing the browser to retrieve the new content.

sample deploy script:

<pre><code>ng build --configuration=production --base-href \"&lt;repo-name&gt;\" &amp;&amp; ngh
</code></pre>

If you don't want a production build, you can also specify output hashing in other build configurations in <code>angular.json</code>

blocks|key|2948619|text|如果使用的是gh-pages命令，则可能需要删除node_modules/gh-pages/.cache中的gh-pages缓存|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2948620|entityMap^0|6|8|O|S|1I|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

If you're using the <code>gh-pages</code> command you may need to delete the <code>gh-pages</code> cache at <code>node_modules/gh-pages/.cache</code>

blocks|key|2735893|text|该问题是由浏览器缓存页面引起的。使用meta+HTML标记禁用浏览器缓存。在_layouts/default.html中添加以下内容|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2735894|<meta+http-equiv="Cache-Control"+content="no-cache,+no-store,+must-revalidate"+/>
<meta+http-equiv="Pragma"+content="no-cache"+/>
<meta+http-equiv="Expires"+content="0"+/>|code-block|syntax|javascript|2735895|2735896|警告:在此之后，任何支持Cache-Control的浏览器都不会存储任何cookies或文件。|blockquote|2735897|2735898|entityMap^0|12|L|0|0|0|C|D|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|U|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|Q|$]]

The problem is caused due to browser caching the page.
Disable browser caching with meta HTML tags. Add the following in <code>_layouts/default.html</code>
<pre class="lang-html prettyprint-override"><code>&lt;meta http-equiv=&quot;Cache-Control&quot; content=&quot;no-cache, no-store, must-revalidate&quot; /&gt;
&lt;meta http-equiv=&quot;Pragma&quot; content=&quot;no-cache&quot; /&gt;
&lt;meta http-equiv=&quot;Expires&quot; content=&quot;0&quot; /&gt;
</code></pre>
<blockquote>
WARNING: After this any browser supporting <code>Cache-Control</code> will not store any of your cookies or files.
</blockquote>

blocks|key|151796|text|在本地提交后，我通过将我的gh-pages分支重命名为GitHub并取消发布我的GitHub页面，然后将该分支重命名为gh-pages，然后再次发布它，从而将我的更改反映到我部署的主页存储库中；然后它就可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151797|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I reflect my changes in my deployed GitHub repository after committing locally, by renaming my gh-pages branch to master and unpublishing my GitHub Page, and then re-name the branch to gh-pages and then publish it again; then it works.

blocks|key|154403|text|只要清除浏览器的缓存即可。ctrl+%2B+shift+%2Br用于Chrome，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|154404|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just clear browser's cache. 
ctrl + shift + r for Chrome, as example

blocks|key|150385|text|在我的例子中，它有助于运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150386|npm运行部署|150387|我是在将主分支推送到GitHub之后完成的。我需要等待一段时间，直到更改在我的页面上可见。但它在没有改变任何设置的情况下确实可以工作。|150388|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, it helped to run:

npm run deploy

I did it after pushing the master branch to GitHub. I needed to wait a bit until the changes were visible on my page. But it did work without changing any settings.

blocks|key|150507|text|您所要做的就是运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150508|150509|+npm+run+deploy|blockquote|offset|length|style|CODE|150510|150511|150512|它会自动更新gh页。|150513|entityMap^0|0|0|1|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

Well all you have to do is to run the following command:
<blockquote>
<code>npm run deploy</code>
</blockquote>
It will automatically update the gh-pages

I've been following the <a href="https://pages.github.com/" rel="noreferrer">official guide @ pages.github.com</a>
So far I've created the local repo and pushed it to GitHub, but, whatever change I do, I can see it in my repo at GitHub but not in my GitHub page. How is that possible?

Why does my GitHub page do not update its content?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我一直在关注到目前为止，我已经创建了本地存储库并将其推送到GitHub，但是，无论我做了什么更改，我都可以在我的GitHub存储库中看到它，而不是在我的GitHub页面中。那件事怎么可能？

问为什么我的GitHub页面不更新其内容？
EN

回答 25

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么我的GitHub页面不更新其内容？EN

回答 25

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么我的GitHub页面不更新其内容？
EN