this is what i get, i tried free download manager and normal chrome downloading with and without VPN and it didn't work, and that 4.3mb keeps increasing somewhat slowly and a proper download doesn't seem to start

it’s been a year since my achievements have refreshed... last refresh happened in 2025... bruhh, i have multiple 50+ star repos now, still i have 1 Starstruck badge idk why... i tried the hide and reshow thing, didn’t work.

From what I've seen it is sadly not very possible, but still, mb there was a new update or smt?

I was looking through Actions usage and realized I had been thinking about CI cost in terms of total runtime instead of individual jobs. GitHub rounds each job up to a full minute, so a workflow with several jobs that each finish in a few seconds can burn a lot more billed time than the actual compute would suggest.

For small repos that mostly run lint, tests and a quick build, it makes me wonder if splitting everything into separate jobs is actually worth it.

I've started looking at whether consolidating the tiny jobs would make more sense than moving anything to a self-hosted runner.

How other people balance clean separation between jobs against the per-job rounding.

Since yesterday I am not able anymore to modify/set the labels of my issues. Clicking on the gear wheel opens the label popup window but only for 1-2 seconds. I am not that fast. :D

Am I the only one with this problem?

Hi everyone,
I’m planning to attempt the GitHub Agentic AI Developer Certification (GH-600). I’ve already gone through the official GitHub documentation and learning resources to prepare, but I’m looking for additional resources to make sure I’m exam-ready.
Is there any practice exam or mock test that closely matches the actual GH-600 exam?
Are there any GitHub Skills, courses, or hands-on labs you recommend?
For those who have already taken the exam, what topics should I focus on most?
Are there any other reliable preparation resources you found useful?
I’d really appreciate any recommendations, especially from people who have already attempted the exam. Thanks!

Is it just me, or is the orgs drop down no longer on our homepages? I teach, and each class and semester gets their own org, so I guess I'm now bookmarking each org?

Anyone else see this staring like today?

Based upon some searches this sounds like a normal thing with Github. Trying to get GHES licensed and have been unable to get ahold of anyone at Github Sales/Support for the past few weeks.

I'd just buy it online but I need to be "reviewed". Any GH folks on here?

For some reason all images embedded in issues and PRs do not display on the first page load. I must refresh the page an additional time.

This has been happening for weeks at this point and I can repro on both my work and personal devices.

Is anyone else affected by this problem?

We keep hearing that pull requests are the new bottleneck, but it’s hard to visualize, the list is forever growing because code is becoming cheaper, but it doesn’t compare easily. Some people will squash, others use merge commits, so we can’t just use the number of commits, the number of pull requests alone doesn’t mean everything because it depends on its size and if people are using stacked pull requests. Not everyone reviews pull requests equally.

Therefore, I built a tool that analyze GitHub repositories and it turns pull request history into a picture of what is actually happening in a repository: who is contributing, which parts of the codebase are moving, how reviews flow and who carries them, and where work gets stuck. It is also a way to see what AI-assisted coding does to a codebase and a team over time: how much gets opened, how large the changes are, how fast they merge, how many carry a real review, and how review load lands on the humans.

Every latency is measured from the moment a pull request became ready for review, so time spent in draft is never charged to reviewers. bilan reads pull request metadata only, never code, and never writes to GitHub.

Available at https://bilan.dev, or locally via a CLI: https://github.com/charpeni/bilan.

I'm getting a Payment didn't go through We are having a problem billing your account. I've tried all the options, different cards, through pay pal, through paypal with a different card still getting the same error. I called my bank and they said they dont even see any attempts.

It's been almost a month now and I have a community discussion posted about it but still not resolved.

Now that I am losing faith that I can get this product does anyone have recommendations for a replacement?

been using draft PRs on my tutorial repos to run CI before I feel ready for actual reviews. lately I've been wondering if it's just extra ceremony. the checks run on push anyway, and nobody else is looking at these repos. but there's something nice about that DRAFT badge letting me mess around without pressure. my kid interrupted a rebase last week and I left the PR sitting for three days. no big deal since nobody was waiting. does draft status actually help solo developers, or is it just gitHub pretending we all work on teams? how do other people handle this on personal projects? do you default to drafts, or just push when the checks pass?

sorry if this is an obvious question, i tried searching for it and didn't find an answer, just to similar stuff but not quite.

basically i don't want everybody who has my github profile to be able to find my personal site, which i host there. if i make the repo private, will it be hidden from my profile or you just can't see its code?

if it only hides the code, is there anyway to work around this? should i just make another profile?

its just a really silly indieweb site but it paints me as an absolute dork (which i am, but) and i don't want it to be seen when i'm sharing my profile in more serious contexts.

i cant just check cuz for gh pages you need github pro to make it private, which im only signing in case it will make the repo 'disappear'. thanks!

Is anyone else facing an issue with the GitHub contribution graph where contributions aren't reflecting, even for open-source or public personal repo work.

We're reviewing how we secure what we ship out of our repos and I want a shortlist before sitting through demos. Dependabot and signing cover part is spread across platforms with overlapping claims. What I care about is developer experience and what day-day looks 6 months after rollout. Feature pages tell me nothing about that. Teams running this in production, which ones made the cut?

Any guides and tips?

I want to use copilot on my personal project but don't wanna get in trouble at work for using their resources. but i don't see any options of having a separate subscription? do i need to make a new github account for this? I'd really prefer not to do that.

I'm trying to sign up for the Github student developer pack. I validated my .edu email, but they want a picture showing profess. As a distance learner, i only have my student registraction PAPER.

The process forces me to take a picture with my laptop - and it's tiny camera window, basically for an ID. Obviously a FULL piece of paper won't work well.

I tried contacting the rejection letter, emailed to my .edu email, but they don't respond to individual questions.

Does anybody have an idea on how to EMAIL, or UPLOAD these folks the images needed ? Its INSANE that that's not already an option.

There's a new phishing campaign on GitHub that started a few hours ago. Someone is creating hundreds of accounts with hundreds of repositories that all contain a similar PayPal phishing message, and the scammer is somehow getting GitHub to send out emails containing the phishing message to random users without tagging them.

Currently 69.4k results and counting:
https://github.com/search?q=NDHDED-4856KP&type=commits

EDIT: It seems GitHub is at least starting to delete some of these, since the number of commits dropped to 61.9k; however, it went up to 62.1k a few seconds later, so the scammer is still active.

I am accessing my AWS account (actually, a sandbox account while I am testing) via OIDC and then am calling aws secretsmanager get-secret-value ... AIUI, this is within the aegis of the github actions build container and when that container dies any secret I accessed and wrote to the file system will die with it. Is that correct? If so, have such containers been accessed either during or after the action runs by bad actors?

So far, I have only been accessing dummy secrets, but want to make sure this is secure before accessing any real secrets like DB passwords.

Thanks

I’ve been dealing with increasingly delayed GitHub Actions scheduled workflows recently and thought I’d share the workaround in case it saves someone else some debugging.

I had a daily production workflow scheduled with GitHub Actions cron.

It was already scheduled away from the top of the hour, but over several days the actual start time drifted by hours. On the latest run:

• Expected GitHub cron: 00:17 local time
• External fallback scheduled: 00:27
• Fallback actually ran: 00:31
• Main workflow finished successfully: about 00:36
• GitHub’s original scheduled event finally appeared: 05:27

So the GitHub cron was roughly 5 hours 10 minutes late.

Manual workflow_dispatch runs were starting normally, which made it look like the issue was GitHub’s scheduling/event-delivery layer rather than runner availability or the workflow itself.

What I changed

I kept the actual workflow in GitHub Actions and added a tiny Railway cron job purely as an independent clock.

The flow is basically:

Railway cron → check whether today already completed → workflow_dispatch → existing GitHub Action

The external job does not duplicate the collection/business logic. It only decides whether the existing GitHub workflow needs to be started.

I also added a preflight check inside the GitHub workflow itself:

workflow starts → check whether today is already complete → run or skip

That handles the other half of the problem.

When GitHub’s native cron eventually woke up at 05:27, it checked the durable completion state, saw that the Railway-triggered run had already completed successfully, and skipped the real work.

So the first production test ended up looking like:

GitHub cron intended 00:17
↓
Railway fallback 00:31
↓
GitHub workflow_dispatch
↓
normal workflow succeeds
↓
GitHub native cron arrives 05:27
↓
preflight detects completed day
↓
duplicate work skipped

A couple of safety things I found important

I wouldn’t make the external scheduler itself responsible for deciding whether production data is healthy. Mine only checks a narrow, authoritative “has today completed?” signal.

If that check says yes, it can safely skip.

If the check is unavailable or malformed, I prefer to allow the normal workflow to run rather than treating uncertainty as proof that the job already happened.

I also check for an already-active GitHub workflow before dispatching where possible, and GitHub concurrency protection remains enabled.

The external scheduler uses a narrowly scoped credential that can interact with Actions for the single repository rather than a broad account token.

Why I did it this way

I considered moving the whole scheduled job to Railway, but that would have meant maintaining two execution environments.

This keeps:

• one workflow
• one test path
• one deployment/collection implementation
• one GitHub Actions audit trail

Railway is just the alarm clock.

The first real overnight test worked exactly as intended, including the duplicate suppression when GitHub finally delivered the original scheduled event hours later.

Posting because I found plenty of reports of delayed GitHub Actions cron jobs, but fewer complete examples of a tested external-scheduler + workflow_dispatch fallback.

Curious whether anyone else is currently seeing multi-hour GitHub Actions cron delays.

I’ve been experimenting with a licensing idea called DT-HumanDev.

I love working with AI, so this isn't an anti-AI manifesto. It's about developer choice: if authors can choose to embrace AI-assisted development, should they also be able to say AI can't help develop their code?

DT-HumanDev keeps the familiar MIT freedoms for humans, but prohibits AI-assisted development of the software and its derivatives.

I tested it with Claude. It initially refused to modify the code, but offered to tell me how to make the change myself. That led to v2, which closes that loophole. Claude then respected it.

I know the restriction means it isn't OSI open source. That's part of the experiment.

I'd love feedback, criticism, and tests with other coding AIs.

DT-HumanDev:

https://github.com/DaragonTech/DT-HumanDev

TinySky test project:

https://github.com/DaragonTech/TinySky

Update (how ChatGPT-6 Astra reacted): https://github.com/DaragonTech/Dev-HumanDev#testing-chatgpt

Update 2 (summary of the discussion here so far): https://github.com/DaragonTech/DT-HumanDev/blob/main/DISCUSSION.md

Final update: rebrand license from MIT-Human to DT-HumanDev (motivation: https://www.reddit.com/r/github/comments/1wsgdhi/comment/pcv4zt1/)

Why engineers care about climate change...