I noticed in a pull request from a colleague the formatting was off, we dobbel checked his local repo and all looked ok on his end.
I tried doing a small change pushed and still same issue, anyone seen anything like this?
File open in vs2022
Same file at github
one more exsamlpe same repo,, diffrent random file
template code seems to use tabs, and all the lines we have touched comes with .... (4spaces)
this seems to break on the github side. case closed.
Let me start by saying that I'm very new to this. I have little to no technical background, so this might just be a simple problem, or I did something I shouldn't have done. It's my first time using the command line and dealing with static pages.
I recently deployed my Hugo site to GitHub pages. I only changed the configuration file, and that's it. (I followed this and this.)
The site is now live at https://USERNAME.github.io/. It's still showing the content of my chosen theme.
A few hours after deploying, I edited some of the local markdown files and pushed the changes. However, the changes aren't reflected on the site.
Now that I realize it, GitHub only displays my site's "public" folder and not all of the files in my local folder.
So, my question is, how can I change and update my site content locally and make sure that the changes are shown on the live site?
Any help is appreciated. Thanks so much!
I have been trying to publish a Sphinx generated documentation for our repository on Github pages with the theme provided by readthedocs.org.
After a few attempts I managed to get it online by uploading the Sphinx generated HTML files in the gh-pages branch of the repository.
Obtaining this:
https://takeqontrol.github.io/qontrol_api/
Which is looking awful, erasing all the customization of the theme by Read the Docs.
Here is an example of what you see if you open the link:
But if I open those HTML files on my computer the pages looks exactly how I wanted them to look.
Here is an example of how exactly the same HTML looks locally:
Does anybody know what is going on? Or even point me somewhere where I can find an explanation?
All the code is available here: https://github.com/takeqontrol/qontrol_api
in the two branches.
I fought with this for 9 hours before figuring out that the underscore in the _static folder was causing the issue.
You need to by pass Jekyll on github pages.
To do this, add an empty .nojekyll to your gh-pages branch. (See example)
I was having a similar issue and then found this, which solved it for me:
Python Sphinx css not working on github pages
Looks like using underscores for the _sources + _static folder caused the issues. Need to rename the folders and paths using them in the html files accordingly.
The current project that I am working on uses Jest snapshots and as it is in the early days still, the snapshots are constantly changing. These new snapshots are filling up my PRs and when diffing files I need to either scroll past them (they tend to be long files) or go through the page at the start and minimize them all manually.
Is there a feature in GitHub or a Chrome extension that would allow me to automatically filter these files out? Even just minimize them?
I've tried Pretty Pull Requests but I can't seem to get it working to recognize the .snap files.
Thanks!
A simple expand / collapse function in the Files Changed view of GitHub will not work? They explained the issue here --> Collapse / Expand files in the Files Changed view of a Pull Request
Otherwise the refined-github extension will maybe help.
Edit with #robdonn comment: Though the collapse/expand function in the refined-github is removed. Previously part of refined-github
Does the wiki that installs with a GitHub repo support directories? Our wiki is cluttered with pages, and we are looking for a way to organize them better.
We tried pulling the repo, creating local directories, and moving things around, but when committed back, the wiki didn't pick up the changes.
I was having the exact same issue and tried variants of what you tried. Nothing stuck. Asked GitHub support about it and received a reply that essentially said "No, but we'll let the developers know that people are interested in this feature."
So the short answer is "No", and the long answer is "No, but maybe in the future."
Actually, it looks like github added support for directories recently.
I was able to do the following:
Move an existing markdown file to a new directory.
Create a new markdown file in an existing directory (created in the former step).
Create a new markdown file in a new directory.
In all cases, the existing pages were still there and new pages were added.
The one constraint that remains is that your file names must be unique. If you have more than one file with the same name, only one of them will show up in the wiki (I'm not sure which.. ).
The GitHub wiki (aka Gollum) does use directories but not in the way you may expect.
The documentation on the Gollum wiki could use some work but this is what I have figured out mostly via testing.
All files appear in the root of the wiki no matter where they are placed in the repo.
_Header, _Footer and _Sidebar files are per-directory, but inherited if there is
none present in a child folder.
File links can be relative to the source file (keep your files with your content).
So, if you want directories for namespacing you are out of luck. Consider using the {namespace}-{page} scheme for namespacing.
It's not the an ideal solution but the workaround would be to create a custom sidebar where you create a table of contents with links to your pages. I find this to be better than folders anyway because it allows you to have a link to a single page under multiple hierarchies.
Actually, there is still a limitation. Yes, you can add 1 level (so, 1 subfolder). But that's it! I refactored my whole documentation layout, creating multiple levels of subfolders for organisation, but that was a no-go.
sigh
I must say: I'm appalled by this Gollum thing. I'm surprised Github even picked it up.
Well, that's a disappointing missing feature!
What I try to do is to actually have directories under a docs directory and in each one, a README.md file.
Not great...but works for documentation and organizes stuff.
If you want to go further, you can have a different branch only with these files.
Still no intention of adding this 9/2022.
https://github.com/orgs/community/discussions/23914