#github pages

[zaigg]

I made a portfolio website for @kaylasartwork! Here's a snippet of it. It isn't live because I can't get Github Pages to work, so any help would be great! (It's having issues verifying the DNS .-.)

Edit: it works now because I'm stupid

You can view the website at https://kaylasartwork.art/

[maniflames]

This week I had to implement continuous integration (CI) with Travis-CI for my work. It took me a lot of build to get it right in any situation. If I push code to this repo a the Jekyll blog gets build and published on github pages.

I am so happy it works I will definitely try to implement CI any time I can.

(The github repo: https://github.com/maniflames/jekyll-travis-test)

[aptivi]

Switching GitHub Pages deployment method from classic to modern method demonstrated with Textify. #GitHub #GitHubPages #GitHubActions #TechNews #TechUpdates #website

Switching GitHub Pages deployment from Classic to Actions-based deployment

[tamzidulhaque]

How to Connect Custom Domain to GitHub Pages in 2026 (Free & Easy Step-by-Step)

Hey friend, Imagine this: You built an awesome portfolio site or a personal blog using HTML, Jekyll, or Hugo. It looks great on yourusername.github.io. But every time you share the link, it feels… temporary. Professional. Then hosting bills hit. $5–$20/month adds up fast. What if I told you there’s a way to host it forever free, with your own custom domain like yourname.com, full HTTPS, and no…

How to Connect Custom Domain to GitHub Pages in 2026 (Free & Easy Step-by-Step)

[sassyquirkstrider]

Top 5 Benefits to Buy Old GitHub Accounts

💡 Why Buy GitHub Accounts? The Big Benefits 🎯

Now, you might ask: Why would anyone want to buy GitHub accounts?

The answer is simple — time and credibility. ⏳ Let’s explore the top reasons why buying GitHub accounts makes sense:

1. 🚀 Instant Authority & Trust

A GitHub account with years of activity, followers, and high-starred repos looks more legitimate than a new account with no history. Buying aged GitHub accounts gives you instant authority.

2. 💼 Perfect for Freelancers & Agencies

If you're bidding on freelance projects or selling software services, showing off a solid GitHub profile can make a big difference in closing deals.

3. 👥 Team Use & Scaling Projects

For companies or agencies, having multiple GitHub accounts allows team collaboration, managing multiple repositories, or running test environments more efficiently.

4. 🔐 Privacy & Separation

You may want to keep your main developer profile separate from client work or business projects. Buying additional GitHub accounts gives you that privacy and flexibility.

5. 🧩 Access to Dev Tools

Some developer tools or beta software require GitHub login or a certain level of GitHub trust (stars, contributions, etc.). A premium account can grant you access to these tools.

We are available 24/7 on What’s App: [phone]

[ricothakarashard]

thakarshard.github.io july2024

Screen Recording 2024 07 22 12.43.01 PM : Free Download, Borrow, and Streaming : Internet Archive

css focus mame I'm playing XMEN:COTA on https://thakarashard.github.io/ and after a SoundCloud song or anything changes window focus I lose

[josegremarquez]

¿ Git hub me permite colgar mi sitio web para hacer pruebas y mostrar al cliente?

GitHub te permite “colgar” tu sitio web para hacer pruebas y mostrarlo a clientes, pero con una importante salvedad: solo para sitios web estáticos. La funcionalidad que te permite hacer esto se llama GitHub Pages. ¿Qué es GitHub Pages? GitHub Pages es un servicio de alojamiento de sitios web estáticos que GitHub ofrece directamente desde un repositorio en GitHub. Esto significa que puedes…

¿ Git hub me permite colgar mi sitio web para hacer pruebas y mostrar al cliente?

[vitaliadev]

Connecting custom domain to github pages.

honestly fuck that shit

I use namesilo for my domain, which is .dev, which by default requires https aka SSL sertificate.

Github Pages provides SSL by default, no need to get new sertificate

Namesilo provides template for github DNS, just click "add Github Template". looks like this depending on where in namesilo you opened DNS:

a. new version:

b. old version:

c. Once button "use template" pressed, the DNS table will update with these lines:

No need to edit anything in them.

4. THE ONLY EXTRA STEP YOU NEED is adding one more line:

Now DNS should look like this, you're done with namesilo part:

5. For github there are plenty of tutorials online, their wiki is enough:

https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https

6. "my site doesn't work" part:

All the errors are related to Github not timely checking shit in order. You just press check again and again and again. delete custom domain and insert again, check "Enforce HTTPS" when it is allowed. "it's not eligible at this time" message is SSL not ready, nothing to do, just wait and check again. Eventually you'll get "the certificate is already created" message on top of the page, so SSL added.

Then it will be "primary DNS is added" in green under custom domain or smth and "www improperly configured" as an error in orange. Still nothing to do, just check again.

Even if "DNS check successful" and you still don't see your site, it is just a matter of doing the same check again, remove, add again. THere's no extra hidden step anywhere. So, the issue in either :

you lack this one line in DNS

you have to delete and add domain again on github (if sll created, you can move from this step imo)

you have to keep "check again"

AND NOT A SINGLE FUCKING ANSWER all over the web with this issue gave a clear visual representation of how it is supposed to look in the DNS table, namesilo or not. Someone just said "add this" and it's description of the last line that has been already added?? JFC

anyways, my custom domain works and I'll eventually update my website using github. right now it is an old site I've done for my CV showcasing what I know from programming (isn't much, hence the post lol)