Some people disable IPv6, or their operating system or device (e.g. router) has IPv6 disabled by default. Is IPv6 support enabled for your connection? If not, edit your network connection (check router as well) in order to enable IPv6 support. A common IPv6 enabled setting for a network connection is this:
Automatic, DHCP only

After enabling IPv6, don't forget to disable your connection and then enable it again, so when you use it to connect to the network the new configuration is loaded. If such change doesn't seem to work, either restart the networking daemon/service or reboot the computer.
Answer from Yuri Sucupira on Stack ExchangeGitHub for Mobile
What's the point of the GH mobile app?
Why GitHub mobile app minimal utilities than GitHub web?
add new repo on your phone! 🎉
Is the GitHub Mobile app free?
Can I write and commit code from the mobile app?
Can I manage organization repositories from the mobile app?
The mobile app has so many limitations that don't exist in the website.
It also requires updates from the store to get new features and bug fixes.
The website is fully responsive, has all the functionalities, updates delivered instantly and quickly.
And if something is missing, it's easily solvable by turning on desktop mode in the mobile browser.
What do you use on your phone? And please leave a comment why
Some people disable IPv6, or their operating system or device (e.g. router) has IPv6 disabled by default. Is IPv6 support enabled for your connection? If not, edit your network connection (check router as well) in order to enable IPv6 support. A common IPv6 enabled setting for a network connection is this:
Automatic, DHCP only

After enabling IPv6, don't forget to disable your connection and then enable it again, so when you use it to connect to the network the new configuration is loaded. If such change doesn't seem to work, either restart the networking daemon/service or reboot the computer.
Start by choosing either Ethernet or Wi-Fi.
In default settings your router is providing IP addresses in both networks in the same IP range, which means your system can get 2 separate IP addresses (IP interfaces) into the same subnet. As an example the router's DHCP server gives your LAN interface IP 192.168.1.10 255.255.255.0 and your Wi-Fi interface 192.168.1.11 255.255.255.0.
Having 2 IP interfaces into the same subnet is a surefire way to invite trouble, unless you use some link aggregation method such as NIC teaming or a redundancy method such as configuring primary /standup adapters.
NIC teaming requires that the receiving end understands aggregation, not a common feature in a SoHo internet router. Primary / standup is a feature of the host alone, but makes little sense. If you use only the Ethernet connection, it's very unlikely to fail completely in the way that would actually require a backup adapter. Wi-Fi connection may experience drops due to signal loss, which is most of the time due to just interference and can be fixed by switching the AP to another channel.
I keep seeing people ask why the GitHub mobile app feels so barebones compared to the web, so here’s my take as a regular dev, not a GitHub employee. Honestly? I think it’s intentional, not laziness. The mobile app feels more like a companion than a full workstation. GitHub probably assumes that real coding, repo management, rebasing, conflict resolving, CI configs — all that heavy stuff — happens on a laptop. Phone is just too clumsy for that, no matter how good the app is. On mobile, the app is clearly optimized for: checking notifications reviewing PRs quickly commenting / approving basic repo browsing staying “in the loop” That’s it. And tbh, that’s all I want on a phone. If GitHub tried to cram Actions configs, repo settings, secrets, branch protections, org admin tools into the app, it would become a UX nightmare. Tiny screen, fat fingers, one wrong tap and boom — production broken 💀 Also, security angle matters. Phones get lost. Web has better control, audits, and serious workflows. Makes sense to keep dangerous buttons off mobile. Another thing people forget: power users live on desktop anyway. GitHub’s core audience is devs sitting in front of a system, not editing YAML on a bus ride. So yeah — the mobile app feels limited because it’s supposed to be. It’s not “GitHub Lite”, it’s more like GitHub Watch Mode. If you expect VS Code-level control on mobile, you’ll be disappointed. If you treat it like a notification + review tool, it actually does its job well. Curious though — what’s the one feature you wish GitHub mobile had but doesn’t? For me? Better diff viewing and search. That’s it.
I can now birth my terrible side projects straight from the app I’m never touching a laptop again
EDIT 2, 8:18pm: I'm surprised how many people thought this unserious post was a celebration of mobile coding… because that already exists, and like most of you I can’t imagine why anyone would prefer to do it. That assumption about my assumption would be incorrect (and unsupported, since I clarified the part about not touching a laptop was a joke).
I don’t see this as a coding feature for three reasons:
-
things needed for actual work still aren’t there
-
creating a repo and coding are not mutually necessary
-
it’s not tied to any other function, let alone one that initiates coding
So it’s not a coding feature; it's a container feature.
Also a bit unfair to assume the GitHub team made that assumption as well. Repos are often created separately from coding sessions, and some repos are created for uses other than coding. So what one does after adding a new repo shouldn’t affect the decision to allow it. We can admit this basic feature feels like a low bar compared to mobile capabilities we already have with literally any other task, which is why people have been asking for it for so long.
On why someone might appreciate this new capability: Ask the many users who have been asking for it for years. Personally, my brain is short-circuiting as it is, and my Notes app is where ideas go to die. Everywhere I put "reminders" adds chaos and extra cognitive load since I know that later I’ll need to remember to fetch it when I'm in the right place and figure out what to do with it before doing it. If something takes 10 seconds then out of my mind, it’s masochistic not to do it immediately. Fewer steps, less to remember, no chance of losing it in a black hole.
Not everyone will want or need this specific feature, just like every app isn't for every user. For those who won't use it, you have permission not to spend time explaining why it shouldn't exist. You are allowed to forget it's there if it’s not for you.
I'm never going to cook with an interactive app reading me a recipe aloud or watch videos on how to chop an onion– but I'd never say the very idea is pointless just because it's irrelevant to me. I don't use it and feel zero obligation to try the features meant for other users. And if it’s in my face I don’t use that app. That's unlikely to happen in this case because this particular function was added to an existing menu, in the same place, with the same + icon. Most users won’t even noticed it.
EDIT 7:28am - I was kidding about never touching a computer again and I don’t even have a laptop. I just meant that it’s finally nice to have the new repo option even if millions of users won’t use it because millions will. In 2026 that basic mobile functionality is expected when almost any work can happen on a phone except creating the place you’ll eventually put it (until now).
I don’t anticipate any serious dev will celebrate the idea and put away their computer. But I also don’t think its reasonable to hate the very idea this feature so much to decide it shouldn’t exist. It’s ok to ignore it. It’s also possible a few people might find it convenient once or twice.
People will make bad decisions with AI anyway so at least with this option they might keep it in folders and out of our faces.
Im a total newbie when it comes to coding and stuff - so i'm kinda confused on how to create a python project and code it using this app.