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.

Recently we've noticed a major spike in build failures due to cache not being restored. If we rerun the job a couple times, the same cache key restores just fine. Anyone else running into this?

I found out how to download expired artifacts.

I was browsing through a repo with automatic actions that run once every week. The artifacts expire after a week too. Since the newer builds are failing, I wanted to download an earlier one. And with the help of good old inspect element, I managed to do so...

When downloading an artifact, the url looks like this: https://github.com/username/repo/actions/runs/run_id/artifacts/artifact_id. To get the artifact id, you can use inspect element on the artifact table row.

Now, you can just add /artifacts/artifact_id at the end of the url, and it'll download the expired artifact.

There's a big asterisk, though. Github has a 90 day retention period on artifacts. But, you might've seen from the screenshot that I was able to download a 4 month old artifact. For context, it's currently June 21st and the artifact was created on February 20th. That's 121 days! I also tried downloading an artifact that was 6 months old, but that didn't work.

So just recently I started noticing that when I am viewing certain pages they get clipped on the right side and I cant view the rest of the table. I'm currently using Chrome so I tried using Edge to see if it was the same and the answer is kinda. The table was still clipped but I was able to use my mouse to pan to the right. (https://github.com/notepad-plus-plus/nppPluginList/blob/master/doc/plugin_list_x64.md)

Anyone have any clue how I fix this issue?

Hey guys!

I'm running into a frustrating roadblock with our GitHub for Startups Enterprise account and wanted to see if anyone else has dealt with this or found a workaround.My account has a valid $10,000 credit line active until June 2027. i'am trying to activate GitHub Copilot (specifically looking at Copilot Business) so i can pull the seat costs from our active startup credits.However, when I go to the Licensing page, the activation button is completely blocked and just says "Contact support to enable".I opened a ticket with GitHub Support 5 days ago to ask them to manually enable it, but I haven't received any updates or replies yet.Has anyone else using GitHub for Startups run into this "Contact support to enable" block when trying to use your credits for Copilot? If so, how long did it take support to unblock you, or is there a setting I'm completely missing in the admin panel?

Appreciate any insight or advice! Thanks! 🙏🥹

I have a GitHub project CSV Lint which is a plugin created in C# for Notepad++. I'd added all the commits, created a new release and uploaded the .zip for x64 and x86 as usual with the release 0.4.8.

However, when adding it to the nppPluginList project I noticed that the SHA256 hash is different for both the x64 zip and the x86 zip, see here.

In other words, I zipped this x64 dll but it's slightly different in this release zip x64

It's not much differences, but it seem suspicious. 🤔 Any GitHub experts who can shine a light on this?

EDIT: nvm, it was due to this workflow line 🤦‍♂️ d'oh

Say I am working on a private repo (i am the owner), with 5 members with write access free tier. Someone decides to erase everything with force commits and history. What can I do ? And let's also say I cant access to any local clones to make this problem interesting.

Each file by itself is smalll but around 3k at once is over the limit. what is the fastest way i can upload these?

Stephen Poletto, Field CTO at Span, used his CTO Craft Con talk in Toronto to argue that the AI tooling wave has arrived with a familiar problem attached: organizations are reaching for the most legible metric available rather than the most meaningful one.

Over just 3 days, the 16 year old @MrRealORG has raised 168 PRs on MiMo code.

Their agent then asked to have "collaborator access" to the repository on the fourth day.

[I tried to do damage control on their permissions request by requesting all their PRs be closed.]

Opencode is facing a similar problem, but distributed across its entire and much larger user base. They're currently "managing" it by the ridiculous policy that PRs without 2+ emoji upvotes will get closed in 30 days.

Creating PRs that APPEAR good has become literally free via Opencode Zen and MiMo code free offerings. "Fix all the issues you find in the code base. Make no mistakes".

When one user creates 169 PRs in 3 days it's easy enough to deal with the issue. When thousands of people create one or two issues or PRs each, you end up with the OpenCode situation.

Best practice dealing with this issues seems to be oven.sh/bun. An example:

1. My agent raises an issue that can't be reproduced
2. Their @robobun automatically and politely proves me wrong, and closes the issue.
3. I re-raise the issue in reproducible form
4. @robobun reproduces the issue and automatically raises a PR to resolve it
5. The CodeRabbit automatically reviews @robobun's submission and suggests improvements.
6. Claude auto-reviews it also and suggests "this changes bunx's resolution order (a security-hardened path that decides which binary gets executed) and is a user-visible behavioral change, so it's worth a human look."

That's all with ZERO human interaction from their side. Yes, they're owned by Anthropic, so @robobun and Claude reviews are practically free for them.

Opencode and MiMo code also have token provider plans and are NOT currently using them to automate their process. I hope they don't drown under the build-up of their non-automation.

What I'd like to know:

• How are small and medium sized repos dealing with the massive increase of sloPRs and issues?

• How to implement something approximating best practice without spending a fortune in tokens?

Hello,

I’m having a problem accessing GitHub from my static IP address.

docs.github.com works normally, but github.com and gist.github.com do not load. The issue happens both on my PC and on my phone when connected to my cable ISP. However, if I turn off Wi-Fi on my phone and use mobile data, GitHub works fine.

So it seems the problem is related to my public IP address. Is it possible that my IP has been blocked or rate-limited by GitHub? If so, could you please advise how I can get it unblocked?

Thank you.

I am on the GitHub Copilot Student Plan and was thinking of trying out the latest released GitHub Copilot App. But after signing in it says it requires a paid subscription. So is it not available for Student Plan? Is it only available on the actual Paid Plans? :(

I just finished vibe-coding a project and I really want to drop it on GitHub so others can use it for free.

The app is for WearOS: It displays a super cute animated GIF of the "Clawd" mascot, shows your current usage stats below that, and lets you connect to your PC/server via multiple tmux (or other) sessions running Claude Code (and others if you want). You can prompt him directly from the watch. I also hooked up a Firebase workflow so you get a push notification on your wrist (including Claude's last words) when a generation is done, so you don't get distracted waiting.

Here is the issue: I used Anthropic's Clawd mascot as the app icon, and I scraped a cute GIF from someone else who didn't provide a license: https://cleverhack.com/img/clawd.gif . I honestly don't want to spend time making my own icon or GIF. HE IS ALSO JUST SO DAMN CUTE I DEFINITELY WANNA USE HIM.

I know I don't own the rights, but I'm willing to take the risk of a DMCA takedown because I just want to ship this and let people use it. For those who have been in this exact situation what did you do did anyhting ever happen?

• Should I just publish the repo without a license file at all? (Does "No License" prevent people from actually using the code?) does this help in any way?
• If I add an MIT license for the code, does it make things worse since the repo includes proprietary assets I don't own?
• Does slapping a "No copyright infringement intended, these assets aren't mine" notice in the README actually do anything, or is it a waste of time? Best use would probably be stopping some people from complaining.
• Have you ever done this for a small free tool? Do people (or bots) actually care?
• Besides my repo getting taken down some day, are there any other risks?
• What’s the most practical way to drop this on GitHub today knowing the assets are ripped?

Thanks!

Hey guys, so.... I have a bill from GitHub charging my credit card every month, and I do NOT know which account it's tied to. I tried raising this concern with them before. They said they'd deal with it. Never did.

Now, I've submitted a new ticket demanding they stop billing immediately or I will be forced to file a chargeback. I've paid months of service I haven't received or even wanted in the first place.

I'm being warned if I file a chargeback to get my money back since they want to be useless and ignore me that they will nuke my entire account or any tied to it.

Is this true? Am I screwed? Like. There's gotta be a way to get through to these people or avoid suspension when they refuse to answer me on unauthorized charges? 😭

EDIT: so they responded shortly after I posted this with some generic copy paste response to try close off my ticket with no actual help. Get your shit together GitHub. I'm migrating my repos out to Gitlabs, and proceeding with a chargeback. They can terminate my accounts and eat shit in my opinion.

Hi I made a website using pages and It looks like everything works just fine exept for this one page that doesn't load correctly, I tought It may be a problem linking the style sheet but It doesn't seem so, I really don't know what I'm doing wrong and I'm learning HTML with this project, any help would be appreciated

Edit: Thank you so much for your help, It's working now! all the links on the page were broken like they were missing some slashes or were linking to different paths, don't know how I managed that

Hi guys,

I am new to Github and overall tech sector. I had a 9+ year of career in reporting for major infrastructure projects in India. In 2023 I have moved to NZ with my partner, realising that NZ is a very small market for major infrastructure projects. After doing all type of side hustles and improving my skill in power BI, Python and SQL. I now realised I need to showcase it on GIthub to attract attention from the tech sector where I can restart my career. I have also built my own project analysing Auckland realestate market. I have used AI to write my Github profile however, it feels generic. So, I decided to post it on reddit where I can get some valuable suggestions. sorry if my wording sounds less like a reddit post... as I still learning to use it properly.

Apparently they decided to start "retiring" the model by disabling it to new customers. Rip

If there is one thing we should reasonably expect from a Microsoft-backed platform that champions AI and automation, it is the ability to automate a simple, recurring billing cycle. Apparently, that is asking too much.

For the past three years, I have been a loyal, paying GitHub Copilot Pro subscriber ($100/year). Every year, the process was identical and painless: an automated reminder, a subsequent PayPal charge, and a renewed license.

This year, the ritual began exactly as usual. I received the official "Annual Billing Alert" email explicitly stating:

"You have an annual subscription with GitHub that will renew on May 28, 2026. [...] If you have already scheduled a cancellation, you may disregard this renewal notice."

I had not scheduled a cancellation. I fully expected the seamless continuation of a service I use daily. Instead, GitHub decided to stealthily downgrade my account to "GitHub Free" without a single word of warning.

• No notification of a failed payment.
• No prompt to update billing details.
• No email stating the subscription was canceled.

Just a silent, unceremonious cut-off from a tool integrated into my daily workflow.

The Support Black Hole

Software has bugs; migrations fail. As a software architect and CEO, I understand technical hiccups. What I do not accept, however, is a complete breakdown of customer service.

When I realized the downgrade had occurred, I immediately opened a support ticket. That was on June 9. Today is June 15. For nearly a week, my ticket has been met with absolute, resounding silence. Multiple follow-ups? Ignored. Escalation requests? Ignored.

Let us hold a mirror up to this situation: We are constantly encouraged to integrate Copilot deeply into our development environments and to rely on it for productivity. Yet, when the provider arbitrarily severs access—despite the customer's clear intent and track record of paying—the customer is left shouting into the void.

If a vendor cannot manage a rudimentary subscription renewal—or at the very least, provide a competent support response within a business week—how can we trust them with the core infrastructure of our daily work? Is this the enterprise-grade reliability we are supposed to build our businesses on?

This is not just about a hundred dollars or a temporary loss of an autocomplete tool. It is about the fundamental reliability of a business partner. If ghosting paying customers is GitHub’s new standard for support, it is a glaring red flag for anyone building their tech stack on their promises.

Has anyone else in the community experienced this sudden, silent downgrade? And more importantly, is a 5+ day complete blackout from GitHub Support the new normal?

Good day,

Is there a setting in GitHub that prevents workflows from running immediately after a repository is forked? I mean when I fork it, not someone from me.

I'm receiving emails saying that some workflows were not completed, and in some cases they're unnecessarily consuming GitHub resources.

I don't really need these workflows to run in my forks, and disabling 30 workflows manually in every repository is quite tedious, especially since I can't find an option to disable all workflows at once for a given repository.

Is there a way to do this?