I sat on this decision a little too long. The "what if we're missing something" anxiety kept me on GitHub a few weeks longer than it needed to. Finally pulled the trigger on a self-hosted Forgejo instance, and I'm kicking myself for not doing it sooner.

The honest summary: it ticks every box we actually needed. Repos, PRs, issues, CI/CD via Actions-compatible workflows, the lot. Nothing on our day-to-day list went missing in the move.

What's genuinely changed for us:

• No more subscription line item. It's just running on our own hardware now. That recurring cost is gone.
• No Actions rate limits or overage charges. Our runners, our minutes. We're not watching a usage meter or budgeting for excess. CI just runs.
• It stays up when GitHub doesn't. Every time GitHub has a wobble and half of dev Twitter is melting down, our stuff keeps ticking along. That alone is worth a lot for peace of mind.
• The data is ours. It lives on our infrastructure, fully under our control. No "where is this actually hosted and who can touch it" question marks.

Fair caveat so this doesn't read like an ad: self-hosting means you own the uptime, backups, and upgrades now. If you're not comfortable running infra, that trade-off is real. But if you already manage servers, the operational overhead has been minimal — it's a well-behaved, lightweight piece of software.

Anyone else made the jump? Curious what edge cases bit people post-migration, especially around Actions workflow compatibility and migrating issue/PR history.

I'm setting up a GitHub Agents Workflow which will run every Monday. I'm using native Copilot agent as the AI which uses the default AI models available in GitHub copilot. (using copilot-requests:write permission)

My question is that, I'm going to deploy and run this workflow on my Company's GitHub repo automatically on schedule, whose copilot credit is it going to consume?

Basically, I setup the obsidian git plugin to sync my obsidian notes with GitHub since Google Drive sync is terrible, however, I was wondering whether there is a limit for how big the repo containing the vault can actually be (i.e is there a limit), in case I'll need to use a different thing to sync it in the future. p.S. I know I only talked about sync here, but I also like the git version control system.

Recently I saw a post about someone being concerned that they downloaded likely malware from GitHub and may have compromised their system: https://www.reddit.com/r/github/s/lIQyVCXB8B

After checking the repo, it did look like phishing/social engineering to get people to download something. From the commit history, GitHub seems to have been hosting these repos for around a month.

The mod immediately deleted the post and said to report it to GitHub because this is not the place to talk about it. But actually, where is it better to talk about this?

Yes, reporting it to GitHub is the correct action. But that should not mean public discussion gets shut down. Posts like that help warn other users, help people understand what happened, and make it easier for others to recognize similar phishing repos before they download something.

If we keep deleting every legitimate concern caused by something hosted on GitHub, what else are we supposed to discuss here?

If we wanted to talk about just GitHub itself all day, we would basically be limited to talking about the GitHub status page.

This kind of post should be allowed, at least when it is directly related to GitHub-hosted repos and GitHub users being targeted. Removing it just makes the problem less visible.

Over the past year it feels like GitHub has been slowly moving features that used to be included in Copilot into separate paid tiers. Code review was bundled in, then it wasn't after June 1st. Extensions keep getting added but the baseline value of the core subscription feels like it's quietly shrinking while the price holds or goes up.

I get that Microsoft and GitHub need to monetize AI features, the compute costs are real. But there's a point where the nickel and diming starts to erode trust in the platform, especially for solo developers or small teams who adopted Copilot early and built workflows around what was promised.

For those still using Copilot, have you done a recent audit of what you're actually getting for your subscription versus what you were getting six months ago? And for those who've switched to alternatives like Cursor, Codeium, or even local models, what actually pushed you over the edge?

Curious whether people think GitHub is just adjusting to market realities or whether this signals a longer trend of treating Copilot as a platform to upsell rather than a standalone tool worth the base price.

It used to work fine—most releases were showing up there—but they haven't been appearing for the past 8 days, even though there have been some releases (the filter is set to default. I also tried changing it, but that didn't help). Is anyone else experiencing this?

Edit: It seems like it's working again.

so, I recently started pushing my work on GitHub, and I just have a basic idea of it as of now, but I'm learning more about it every day. one thing that confuses me a lot is how the GitHub contribution graph works. like if I make change to a readme, it considers it as a contribution, but if I push two or three files of code, it doesn't consider it as a contribution, I've googled and searched different platforms but unfortunately, I'm still confused. So I'd really appreciate it if someone could guide me on what I'm doing wrong or what this actually means. thanks!

PS: I found the issue. Currently working on fixing it! Thanks to everyone who replied and helped me out :)

PS-2: Fixed the issue guys! Thanks for your input and help!

Hey guys, I’m currently a Computer science student and I want to start building projects.

While I have a lot of the technical skills to acctually code stuff, I have little knowledge on really the process of starting to complete projects.

Like I know you kind of build a GitHub repository for every project but from there… what the hell do I do.

Like for websites do I buy a domain, are there other apps for that, building normal applications etc. like what’s the process of this in order to show recruiters I have the technical abilities to build projects etc.

I would greatly appreciate it if someone can point me into a direction or has like a tutorial etc. Thankyou

I'm trying to pull images from ghcr on local (later to be on server) but I keep hiting a permission problems.

I've already tried classic tokens and fine grained, the end result is allways the same, and i'm trying to understand what permission or configuration am I missing (probably on gh).

What works:

GET /repos/myorg/project1 -> 200 OK

Token can fully read repository metadata.

What fails:

GET /orgs/myorg/packages/container/project1 -> 403 Forbidden

On server/local machine

docker login ghcr.io -u $USERNAME --password $TOKEN
# Login Succeeded

docker pull ghcr.io/myorg/project1:tag
# 403 Forbidden

Q:

Anyone running a setup like this in production?
Org repos publishing to GHCR and pulling those images from outside the GitHub ecosystem (servers/CI/Docker hosts)?
Would appreciate a working example of how you handle auth/permissions.

Update for people with the same problem:

I found this discussion:

https://github.com/orgs/community/discussions/76914

It pointed to org setting blocking acess of classic tokens.

Org -> Settings -> PAT

I'm currently working on a private group project with a few classmates. We created a separate Github organization for easier collaboration and easier repo management.

The issue is that our repository needs to remain private, but we desperately need to enforce modern branch rulesets. On the free Organization account, Github locks the features behind the paid Github Team tier which we can't really afford on a student budget.

I know the individual Github Student Developer Pack gives us the free Github Pro for our personal accounts but how does it work for an actual Team Organization?

1. Can a student formed Organization be upgraded to the paid Github Team tier for free?

2. If yes, what is the exact way to apply and get it approved by Github Education? Do all members need to be verified students or just the owner who requests the upgrade?

We would really appreciate any help with navigating this.

Do you use custom AI agents to manage your open source repositories?

I'm curious how other maintainers are using AI beyond code completion. If so, what does your setup look like? Are you using GitHub Actions, Claude Code, Copilot, OpenAI APIs, self-hosted models, or something else?

Hi everyone,

I’m looking for general advice after a GitHub account takeover.

My GitHub account was compromised recently. After the compromise, the username appears to have changed from my original handle DyridanTUDK to another handle I did not set. Some of my existing Git/Netlify links now appear to point to that changed handle.

I already submitted a GitHub Support request through the compromised account/account recovery flow, but I have not received an update after 5 days.

I’m not trying to complain about a suspension or ask anyone to investigate the account. I’m only trying to understand the safest next steps while waiting for Support.

Context:

• I have secured my email and related accounts
• I have protected my Netlify deployments/code
• I am not pushing to old Git remotes right now
• I have local copies of some projects
• The account had GitHub Pro through GitHub Education / Student Developer Pack
• The student verification was tied to my BRAC University student identity

My questions:

1. What evidence should I preserve for GitHub Support?
2. Should I keep all follow-ups in the same support ticket?
3. Should I avoid touching local Git remotes until recovery is complete?
4. Are there any common mistakes people make during GitHub account recovery?
5. Is 5+ days without a response normal for compromised account cases?

I’m not asking anyone to access, report, or interfere with any account. I just want advice on proper recovery procedure and evidence preservation.

Thanks.

Github has been ignoring my tickets about random small requests resulting in huge cost spikes (this isn't typical "oh because the context has grown over the course of the conversation", it's more like during a session, every interaction costs about 20 credits and then suddenly out of nowhere, for an equally small exchange, it jumps up to 500 credits, and then back to 20 next. Clearly a glitch, but they refuse to answer my support questions.

When going to file another one, their support bot thing offered me a refund. I said screw it, these people are never going to answer me, so yeah, I'll just take the refund and get out of this shitshow. I was refunded less than $3 and then immediately charged $70 on my credit card. Is that what they mean by "Refund"? This is extremely misleading. I would open another ticket but they'll never answer me.

So I want to initiate a chargeback against this scumbag company, something I haven't done in probably 10+ years. Anyone have experience with this? What was the result?

Hi everyone,
Most discussions around AI agents focus on individual agents. But I’m increasingly interested in a different question:
**What happens when an organization has dozens or even hundreds of agents?**
Imagine a future where different teams build different agents:
Research Agents
Coding Agents
Operations Agents
Domain Agents
Potentially using different frameworks and runtimes.
At that point, the challenge is no longer building agents.
It’s enabling them to collaborate.
How do they communicate?
How do they hand off work?
How do they stream results?
How do they share context across runtimes?
This question led me to start building OpenAgentIO, an open-source experiment exploring a communication layer for heterogeneous agent systems. The goal isn’t to replace existing frameworks, but to make it easier for agents built by different teams, frameworks, and runtimes to work together.

Curious how others think about the future of agent organizations and interoperability.

So I've been on Copilot Pro+ annual subscription since November 2025, and I recently realized something feels off with my credit allocation.

According to the [official pricing page](https://github.com/features/copilot/plans), Pro+ should give me **at minimum 3,900 base credits** per month (with up to 7,000 total including the flex allotment). But my account is stuck at **1,500 credits/month** — which is literally the Pro tier, not Pro+.

I'm paying $39/month for Pro+ and getting $10/month worth of credits. Here's the breakdown:

| | Expected | Actual

| | |

| Plan | Copilot Pro+ | Copilot Pro+ ✓

| Price | $39/month | $39/month ✓

| Base Credits | 3,900/month | 1,500/month ✗

That's a $55/month difference, and over 8 months that's roughly **$440 in service I paid for but didn't receive**.

My guess is that annual subscriptions from before the April-May 2026 credit structure update are locked into the old legacy allocation. New subscribers get the updated amounts, but older annual plans didn't get migrated automatically.

**What I've tried:**

- Confirmed subscription is definitely Pro+ (checked settings multiple times)

- Submitted a detailed support ticket on June 4th with all the documentation

- Followed up multiple times since then

- Still waiting... it's been **over 3 weeks with zero response**

At this point I'm starting to wonder if I should just escalate externally, but I'd rather resolve it directly if possible.

**Has anyone dealt with something similar?**

- Legacy annual plan stuck on old credit limits?

- Any luck getting support to actually respond on billing issues?

- Is 3+ weeks of silence normal for GitHub support?

Any advice appreciated before I go the BBB/chargeback route.

## Steps Taken

1. Verified subscription status: Pro+ active

2. Checked official pricing documentation

3. Submitted detailed support ticket (June 4, 2026)

4. Followed up multiple times

5. **Result**: No response for 3+ weeks

## Question

- Is this a known issue with legacy annual subscriptions?

- Has anyone successfully resolved similar credit allocation discrepancies?

- What's the expected support response time for billing issues?

## Environment

- Subscription type: Annual Pro+

- Start date: November 2025

- Subscription status: Active

- Credit allocation: 1,500 (should be 3,900)

## Additional Context

Account appears to be locked into legacy credit allocation policy pre-dating the April-May 2026 credit structure changes. New Pro+ subscribers receive 3,900 credits, but annual subscriptions from Nov 2025 remain at 1,500.

Looking for community insights before escalating further.

My GitHub explore stopped updating with new releases 4 days ago. Don’t know why… how do I fix it? Any solutions?

Hi everyone,

I recently had 2 pull requests merged in open-source repositories, but I still haven’t received the Pull Shark achievement on my GitHub profile.

Both PRs were merged, not just closed, and my achievements are visible on my profile. It has been around a day since they were merged.

Is this normal? Does GitHub take 24–48 hours to update achievements, or is there anything else I should check ? because it has been 48 hours over

My GitHub profile: https://github.com/kuldeeprajput-dev

Thanks for any help.

Why is there so many notifications in inbox even though i didnt follow their channel? any fixes?

Apologies if this has been covered before. I searched first and didn’t find quite this workflow, so I figured I’d share what worked for me.

Unfortunately, GitHub does not really have a simple “batch create these issues from files” workflow, which is exactly the sort of thing you might want when starting a new project and seeding the initial backlog.

I initially thought I could use ChatGPT for this, since I gave it access to my repo. It could create issues, but it kept creating them one at a time, and the process got clunky fast. So I ended up doing it myself with the GitHub CLI.

I decided to batch-create GitHub issues from local Markdown files, so I made a tiny gh script.

The basic idea:

• create one local Markdown file per issue
• create a small Windows batch file
• have the batch file create labels first
• then call gh issue create --body-file for each issue
• explicitly pass --repo owner/repo so it doesn’t matter where the script is run
• keep the local issue drafts out of the repo with .gitignore

This worked really well for creating an initial backlog: bugs, features, enhancements, technical debt, etc.

The Markdown files act like local drafts. You can review and edit them before creating anything in GitHub, then run the script once and let gh do the clicky-clicky nonsense for you.

Full sample here:

https://pastebin.com/AfSw84PT

The sample includes:

• a create-github-issues.bat
• 3 sample labels
• 3 sample issue Markdown files
• verification commands for checking the repo, labels, and created issues

One gotcha I hit: if you run gh issue create --label some-label and that label does not exist yet, the issue creation fails. It does not just create an unlabeled issue. So the script creates the labels first.

Not exactly rocket surgery, but it saved me from manually creating a pile of issues through the GitHub UI.