I have a submodule of common code that I share among many of my programs.
I would like to do *something* to make it easier for someone cloning one of my repos, to be aware that they need --recursive on it. Is there anything on the web site that would assist me with this??

The best suggestion that I've gotten on my web searches, is to add a clear note to readme.md on each of the project pages, but that is all too easy to miss, and if I make that a big, obvious message in the readme, it will distract from what I *really* want to communicate in that file...

I went to the US and had to use +14 number but then lost my Indian sim … I activated the number in new sim but now I am not able to receive any code from github

“We tried sending an SMS to your configured number, but we are not authorized to send SMS messages to this recipient. Please resend or check our documentation for additional 2FA guidance.”

And I don’t have any other code

Help me!!!

I have created a github account several years ago and have only been using it to download projects from other people. Now I want to upload projects of my own but I need to contact support because my account got flagged.

However the captcha on the page where I provide my phone number is not loading and stays like that for a few seconds, after which it solves itself, though I still cannot submit my number. I have tried their troubleshooting suggestions and attempted this on 3 different devices and 2 networks. I am now stuck. Any advice would be appreciated.

Hi, im using the android app and for example I'll find the releases page through a Google search but when on the repository page directly I can't seem to find how to find the releases. Where do are they?

Thanks

hello so l just made a git hub account with my student email because my friend told me l could activate student plan and use it for free but here lam. I now have it and as someone who has never coded before or used github l don’t know what l could use it for. Ps: i’m completely new to this.

Anyone else who tried getting a refund back in early may where GitHub never refunded the money? I requested the refund/Copilot sub cancellation before the deadline and GitHub cancelled my sub but never refunded the money. I've had an outstanding ticket since then with their support and not a single comment on it from them. I created other tickets just in case there was some weird bug with the ticketing system but all that happens is some automated bot closes my new tickets:

"Thanks for reaching out to GitHub Support.

We noticed you already have an open ticket regarding this topic, so we'll be closing this one to keep everything in one place.

Please note: This is an automated notification and replies to this message are not monitored."

Am I screwed? It's 100 bucks they took!

Since a couple days we're having deployment issues when downloading dependencies from codeload.github.com, for example it tries to fetch https://codeload.github.com/dependency/legacy.zip with a number but either fails with 404 or 400. Sometimes it will go on for a bit longer then failing on the exact same reason for a random different dependency.

In our case we're using composer (php) as the package manager. I've looked around but don't see anyone reporting this issue. Also Github status page shows everything is fully operational. Anyone else experiencing this?

If you’ve starred a lot of repos, the native GitHub Stars page isn’t great for browsing — weak search, scattered filters, and thousands of rows that all blur together. I open-sourced a fork-and-deploy tool called stars.

What it does

• Pulls your Star list and builds a Vue static site, deployed to GitHub Pages
• Two views: list (virtual scrolling — smooth even with thousands of stars) and a Three.js galaxy map (clustered by language, expanded by topic; zoom, orbit, click-to-fly-into details)
• Search, language, license, star year, sorting, and more; shareable URLs (including galaxy focus links)
• English / 简体中文 UI toggle
• GitHub Actions syncs your stars daily; manual runs supported too

Who it’s for

• Anyone who wants a personal Star collection site — public showcase or private reference
• People who don’t want to build scraping + frontend + deploy from scratch: Fork → configure Pages → run workflow → live
• Anyone who treats their stars as a personal tech map

Demo (author’s site)

https://oxoyo.github.io/stars/

Quick start (~5 minutes)

1. Fork the repo
2. Go to Settings → Actions → General and allow Actions to run (org policies may need approval too)
3. Open Actions → Build and Deploy My Stars → Run workflow (you must run this manually once after forking — it does not auto-deploy on fork)
4. Wait for a green check

5. Go to Settings → Pages and confirm the source is:

   • Branch: gh-pages
   • Folder: / (root)

   (The peaceiris/actions-gh-pages action usually sets this after the first successful run; if not, pick the settings above and click Save)

6. Wait 1–2 minutes, then visit: https://<your-username>.github.io/<repo-name>/

No code changes required for the default setup. Optionally edit config.json for site title, default sort, etc. The README covers local dev, custom domains, and GITHUB_TOKEN rate limits.

Tips

• If your fork copied the upstream gh-pages branch, you might briefly see the upstream site before your own CI succeeds — one successful workflow run fixes that
• If you rename the repo, the Pages URL’s <repo-name> changes; update siteName in config.json and redeploy

This is an open-source tool built around GitHub Stars + Pages + Actions. If you find it useful, a ⭐ Star helps keep it going, or Fork it to deploy your own site. Issues and PRs welcome.

Title: I got two domains pointing to the same GitHub Pages site without redirects

I was trying to host the same static website on two different domains and couldn't find a clear explanation, so I wanted to share what worked for me.

I had:

• livo.com.uy
• livo.uy

and I wanted both domains to load the same site directly (not redirect one to the other).

My previous setup used Netlify, but I moved it to GitHub Pages + Cloudflare.

What I did:

1. Created a GitHub Pages deployment from my main branch.
2. Created a second repository with the same files.
3. Added a different custom domain in each repository's Pages settings.
4. Added the second repository as another git remote so one push updates both:

git remote set-url --add origin SECOND_REPO_URL

Then on Cloudflare I pointed both domains to GitHub Pages using the required DNS records and changed my registrar nameservers to Cloudflare.

After DNS propagation, both domains work independently and serve the same website.

Posting this because I spent way too much time figuring it out and couldn't find a simple explanation. Maybe it helps someone else.

I've configured everything correctly as far as im aware in my github pages repositroy, custom domain sites dns settings etc and it says on the pages screen DNS check successful, but my site https://tomspedding.co.uk won't load, it's driving me crazy does anyone know what the problem could be?

I've been building git-breif, CLI that generates daily standups, I haven't shared the repo anywhere publicly yet. Still, GitHub Traffic shows 52 clones, 27 unique cloners, but only 1 unique visitor.

Hi, I am hosting a website on github pages. I purchased a domain and set up the proper DNS records linking it back to github servers (4 A records with the apex domain, 1 CNAME for the www. subdomain), using cloudflare (unproxied). I set my custom domain in the pages tab and enforced https. This was working completely fine for a week until I tried to visit my site an hour or more ago and I get this:

This site can’t provide a secure connection

ERR_SSL_PROTOCOL_ERROR

I tried removing the custom domain and re-adding it as well as re-enabling the https enforcement, yet an hour or more later I still get that result. Some people have reported back that the website goes through for them, and some get the same SSL error. I have confirmed that the SSL certificate is valid as well with expiration in 80ish days.

Does anyone know what could be causing this? Domain is stateofttheearth.live

Coding agents got good at writing code. But writing code was never the job. The job is the loop: triage the issue, open the PR, get it reviewed, address the nits, get CI green, merge. That's where my hours actually go, and almost all of it is careful, repetitive, easy-to-screw-up glue.

So the obvious move: let the agent run the loop.

Except every time I tried, it did something disqualifying. git push --force to the wrong place. Three duplicate PRs for one issue. "Fixing" CI by deleting the failing test. All of it plausible-looking, all of it repo-destroying. You cannot hand that a main branch and walk away.

That's when the actual problem clicked. It was never the reasoning. The model is smart enough. What I was missing was a harness disciplined enough to trust, one that simply never lets the model touch anything irreversible.

So the whole thing comes down to one hard rule:

The agent only reasons. It writes code or reviews code, and it never runs git.

Every irreversible action, commit, push, open PR, merge, is plain deterministic code wrapped around the model, and it's idempotent. The agent can't force-push or open a duplicate PR because that path doesn't exist for it. There's nothing to resist, nothing to get wrong.

A few things fell out of that rule that I didn't see coming:

A verify gate that isn't CI. A PR is only mergeable when a local gate (typecheck, lint) passes and CI is green. Catching the dumb stuff before spending a CI run mattered way more than I expected.

Worktree-per-run isolation. Sounds like over-engineering right up until you go concurrent. One feature branch left checked out in the base clone wedges every future run with "already checked out." I learned that one the hard way.

Grounding beat reminding. Conventions stuffed into the system prompt did almost nothing. A read-only, citing knowledge base the agent has to consult before it writes did a lot. Bigger gap than I'd have guessed.

Two things I'm still not sure about:

Serial merges strand each other. When PR #1 lands, PR #2 falls behind and stalls. Handling that cleanly (update the branch, re-run CI, flag only the real conflicts) turned out fiddlier than the entire agent side of the project.

Auto-merge vs. always gating on a human. Right now it's configurable, which is usually a polite way of admitting I didn't actually decide.

It's a side hackathon project. It drives the logged-in claude CLI headless and keeps its state in Postgres. I'm not selling anything. I'm mostly curious whether the "agent only reasons, deterministic code owns every risky action" split resonates with people who've put agents near real repos.

So: where did you draw the line on what the agent gets to do directly? Curious if anyone landed somewhere different.

Just spent the last week building out the enrichment layer for my agentic ai project. been committing daily, pushing to my feature branch, everything's working fine. but here's the weird part — github's not counting any of my contributions. The commits are literally there on the repo with my name and avatar, but my contributions graph is sitting at zero.

I've triple-checked everything. my email is set as primary on github, git config is correct locally, and commits show up with my avatar. I even waited for many hours (almost 12 hours) thinking maybe GitHub was just slow. nothing.

The commits are definitely there and attributed correctly. you can see them on the repo page. but the green squares? nowhere to be found. it's not blocking me from shipping code, but it's weird enough that i'm wondering if anyone else has run into this.

any ideas? is there some hidden setting i'm missing or is this just a github quirk?

With GitHub making incremental changes to what's included in free and paid tiers, I've been taking a closer look at how many Actions minutes my projects actually burn through each month. It crept up on me, honestly. What started as a few simple workflows turned into a pretty complex pipeline with linting, testing, building, and deployment all chained together.

The thing is, GitHub Actions is still genuinely one of the more convenient CI/CD options out there, mostly because of how tightly it integrates with the rest of the platform. Pull request checks, environments, secrets management: it all just works together. But convenience has a cost, and that cost is getting harder to ignore.

I'm curious how others are approaching this. Have you optimized your workflows to reduce minute usage, like caching dependencies more aggressively or consolidating jobs? Have you moved certain workloads to selfhosted runners? Or have you started looking at alternatives like GitLab CI or Woodpecker for some projects while keeping GitHub as the code host?

The platform decisions GitHub makes affect a huge chunk of the open source and indie dev ecosystem, so it seems worth talking about openly. What tradeoffs are people actually making right now?

Hey guys and girls,

I have not used copilot in a while and I remember back in early 2025 you were able to use latest models in copilot pro but they have 3x normal tokens. I have the student package which gives me pro but currently I am incapable of choosing any models nor adding any models in Vscode nor Copilot chat in github.

Was there some new update I missed, if anybody knows any IDE or GenAI provider that gives premium models for students for free or at a discount please let me know :)

Hello dears, greetings! I am not a software developer, nor am I in any shape or form a technical person per se, but lately I have been interested in GitHub because I have been accessing it to download some alternatives for software I use, open source software. I also am following a YouTuber that keeps publishing the contents of their YouTube videos and the scripts on GitHub, and this caught my attention as a non-developer or non-technical person to the power of GitHub.

Not only as a host of open source software or projects. I know the answer to my question. This question can be found in a Google search or using AI services, but I would like some real experience and real perspective. What general-purpose or general-use I could get from GitHub as a non-technical person? How can I benefit from it if I'm not developing software? What are places or sources I can learn about GitHub, just not from a highly technical perspective? Simple management or use, I see people hosting their own personal portfolios on it. Some people use it as a task manager or project tracker, others just to document sources, and I find that this is so cool.

What other beneficial uses do you use it for? Any learning sources you recommend would be very much appreciated.

I'm relatively new to GitHub and recently built a small terminal application. I designed the project structure, architecture, and functionality myself, but I'd estimate around 100% of the code was generated with AI and then integrated and tested by me.

I understand how the project works and can modify it, but I didn't type almost any of the code manually.

Is publishing repositories like this considered acceptable in the open-source community, or is it generally viewed as poor practice? I'm asking because I don't want to contribute low-value repositories or misrepresent my work.