Github pages do not seem to work when certain files are modified #151795
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I have been running this site for quite a long time, which explains why I'm deploying from the "old"
gh-pages. I'll cut to the chase: it seems to trigger, and then deploy, only in some cases; when a file calledindex.mdis modified, it does not even trigger.Since this workflow does not seem to be controlled by a github action present in the repository, I have no idea what can be done about it, other than the workaround of actually modifying other file and see what happens. Or I may have missed some announcement by which these kind of deployment workflows became deprecated last week or so. Any way, help will be appreciated.
P.S. If there's something special about that file, is that it's generated by a post-commit hook and not present in the main branch. It's generated from
README.mdin the main branch, but could it be that it's triggered only when a file in the gh-pages branch which is also in the main branch is modified? It's a longshot, but I have no other explanation.Beta Was this translation helpful? Give feedback.
All reactions