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.
Related
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 am trying to embed a google docs in Github's readme.md using markdown. Is this possible?
I have done the following:
Published the document to web and copied the iframe code.
Pasted the code in markdown. Nothing happens.
Pasted the code between and nothing happens.
Any suggestions?
This isn't possible. When GitHub renders a README or other text document on the site, it gets passed through a filter to sanitize it and remove anything potentially malicious, including JavaScript and iframes. That's because these documents are rendered in the context of the github.com domain, and any malicious code could steal user credentials or otherwise create privacy or security problems.
Note that even if you could bypass the sanitizer, GitHub sends a Content-Security-Policy header that restricts JavaScript to a single, specific domain and rejects all frames, so your browser would not render such content, and it would use the report URI to send a notification to GitHub that a violation had been detected.
You could save the Google Doc as Markdown, AsciiDoc, or HTML and place it in your repository for people to use if you want it to be visible on GitHub.
I have just created my first jekyll page, trying to use github.io
What am I doing wrong, as the page seems to serve correctly on my local machine yet it does not on the GitPages.
If you want to use a github.io URL, the exact URL of your GitHub page depends on the name of your repository.
This is explained here in the GitHub Page documentation:
User, Organization, and Project Pages
If you want your website URL to be https://cstml.github.io/ (called "user page" in the docs), the repository must be named username.github.io, i.e. in your case:
https://github.com/cstml/cstml.github.io
If you want your website URL to be https://cstml.github.io/some-sub-dir (called "project page" in the docs), the repository must be named some-sub-dir, i.e. in your case:
https://github.com/cstml/some-sub-dir
In my search for trying to solve it I have changed the name of the repository to my cstml.github.io GitHub-pages and that seems to have fixed it. Don't really understand why that is at the moment but it seems to be working.
I am trying to figure out how to setup github pages for account rather than for a repository.
E.g
I want the blog address to be like this:
xxx.github.io rather than xxx.github.io/repo. Therefore when i go to xxx.github.iothe static markdown pages should appear rather than a 404 page.
Thanks.
You're looking for Pages' user / organization sites. The official site has a good getting started guide, but the first bit is the most important one:
Create a repository
Head over to GitHub and create a new repository named username.github.io, where username is your username (or organization name) on GitHub.
If the first part of the repository doesn’t exactly match your username, it won’t work, so make sure to get it right.
So, instead of creating a gh-pages branch as you would for a project site, you must create a repository that matches your user name.