If I have a private GitHub repo with two public pages
example.com/index.html
example.com/my-super-secret-url-362956393.html
and it is hosted on a private repo. Obviously, anybody could find example.com/index.html as it would be the default link, and could see any pages it links to.
Is there anyway someone could find the secret page without it being directly linked to on a sitemap, or as an tag on another accessible page?
Related
Problem
I have deployed the website through github page, custom domain, and the articles are accessible normally. But copy and paste the article address, open a new page in the browser, paste the article address, the page 404. I can confirm through the text comparison tool that they have exactly the same link address, after accessing the home page through the custom domain, click on the article can be accessed, directly accessing the article (not accessing the index.html home page of the custom domain), will 404. this 404 page is not This 404 page is not the 404 page of the theme, but the 404 page of the github page.
The steps for reproduction are as follows:
visit guowei-gong.github.com
click on any article
copy the address of the article (either directly from the address bar or by copying the article address at the end of the article)
Open a new window in your browser
Paste the address of the article and reproduce it
I tried to find out if anyone else was experiencing the same thing as me and came across one of the 2015 discussions (Fargo discussion) where they thought it had something to do with the repository of the github page, if that repository is your username then it always resolves the main branch and the other repositories resolve the gh-pages branch. I'm currently using a repository named after my username before I cry, and I've changed the Branch under Repositories -> Settings -> Pages, as shown below. Could this be the cause of this problem? I'd like to try deploying directly to the main branch as a next step.
Supplementary
Now I've tried deploying in the main branch and it's been 15 hours and still the same problem!
I cancelled the Github action workflow deployment and pushed the locally generated static page directly, and I was able to make sure that the static page looks fine locally. Here is the github repo address.
I have created the portfolio website using HTML5 and uploaded the respective files in the GitHub with new repository, but I cannot able to view the url link like (it is published at...) shown in YouTube videos.
I searched GitHub pages under the "Code and Automation" tab, still I cannot able to view the URL.
Can somebody please help me where to view my portfolio?
Note: GitHub Pages now uses Actions by default
It means that, instead of configuring a publication source (a branch or docs/ folder), you can add in a .github/workflows (inside your repository) a actions/starter-workflows pages/static.yml in order to publish your static HTML5 pages.
My GitHub Pages site is built from the master branch, using my README.md. The top of my read-me file is directly below.
# :chart_with_upwards_trend: :robot: Wooster Systems :moneybag: :money_with_wings:
This looks just fine in the read-me inside the repository. Image below.
Unfortunately, the workflow status badges don't populate on the Jekyll GitHub Pages site. Specifically, the badges that come directly from GitHub don't show, but the rest do. The ones that don't show are tests, firebase deployment, and pages-build-deployment. A screenshot from the site is below.
I'm not sure why this is happening. My hunch is that it has to do with the fact that my repository is private, but what has me confused is the fact that the coverage badge comes from an SVG file directly in my private repository. This works fine on the site (possibly has to do with "artifacts", though I don't really understand the behavior). If the workflow badges are indeed private, how can I make them display on my site?
The only config file (or file that has anything to do with the GitHub Pages site) is my _config.yml, which has the following contents.
theme: jekyll-theme-cayman
plugins:
- jemoji
I installed added jemoji to support the emoji shortcode in my title, which works fine.
Any help appreciated.
Private repositories are not publicly visible. For security, any requests to them from an account without the right credentials will get a 404, so you can't guess which repositories exist.
Because the repository isn't available, your workflows and their results aren't public either. If you want a developer on your team to have the build status, invite them to your private repository. If you want your builds to be publicly visible, open source your repository.
It can be because this tags are alterated because of github actions, so they update and change on the Repository, Github pages treats different the information so this tags are nos updating when you are accessing the web page.
Live tags from Shields.io doesn't work properly on github pages.
I'm just a regular user on GitHub. I don't have an enterprise or anything like that. I was wondering can I still create a https://myusername.github.io/ page like a blog or portfolio, and can that page contain links to individual repo github pages like https://myusername.github.io/myrepo1 That way this can act like a portfolio website.
Is this possible? I keep having issues with setting up the https://myusername.github.io/ page but the repo-based url works fine and is easy to set up
A User GitHub page will contain markdown files which, in turn, can include any URL you want.
Incuding URLs referencing your other repositories.
I created a page for a github repository following these instructions:Getting Started with GitHub Pages. Worked perfectly, the page is already hosted.
But I would like to change the page URL, This is the currently URL: http://myusername.github.io/repositoryName/
Is there any way to remove the repository name? (http://myusername.github.io/)
I've seen the articles to configure a custom domain, but I think that's not the case.
To remove the repository name, you'll need to make it a User Page (or an Organization page). Create a repository named myusername.github.io, and commit your content to the master branch. See this help page for more information.