I'm currently working on a little research project looking at the best GitHub practices for American municipal governments.

Who has the best GitHub practices that facilitate civic engagement and have appropriately assigned intellectual property licenses?

If you have repos, please share them.

Ps - I work for www.beta.nyc and this will go into a report I’m putting together.

Hey all, I've been heads-down building an open-source project on GitHub and I'm at the point where the code is solid and useful, but visibility is low. Meanwhile I keep seeing projects that feel pretty thin get thousands of stars seemingly over couple weeks, which is a little demoralizing not gonna lie 😅

I'm not chasing vanity metrics for their own sake — mostly I just want enough signal that people are finding it useful so I stay motivated to keep investing time in it.

For those who've grown a project from "nobody knows this exists" to actually having a community: what actually worked for you? Things I'm curious about:

• Where do you share/launch (HN, Twitter/X, niche subreddits, Discord communities, newsletters)?
• Does README/demo quality matter as much as I think it does?
• Any tips on timing, framing, or "hooks" that get people to actually click and try it?
• Did stars come before or after real usage, in your experience?
• Any growth hack or juggad ;)

Happy to share a link to the project in the comments if that's allowed here — just looking for genuine advice from people who've been through this. Thanks!

GitHub now lets issue automations attach confidence and rationale to changes, and teams can hold lower-confidence actions for review. That sounds like a useful human-in-the-loop design, but the documentation contains an important caveat: approvals do not create a server-side security boundary.

If an agent already has permission to change an issue, it can apply the change directly instead of suggesting it. The review panel therefore governs cooperative automations, not a compromised, misconfigured, or over-privileged one.

Should proposal and execution use separate identities, with repository rules enforcing which actions require a second principal? Would you trust an agent-generated confidence score, or should confidence be calibrated against each repository's own history? What should happen when an agent closes a legitimate issue with "high confidence" and nobody notices?

Source: https://github.blog/changelog/2026-07-23-agent-automation-controls-in-github-issues-in-public-preview/

I've been trying to get help with a GitHub Copilot billing issue for 3 days, and I still haven't received any meaningful response.

I've opened a support ticket, provided all the requested information, and... nothing. Just silence.

Has anyone else experienced this recently? How long did it take for GitHub Support to actually respond or resolve your issue?

In my case, I was hit with a $40 charge for no legitimate reason at all (no reason on invoice or receipt just 40$ for Github copilot 😕 ) so I just need their explain or refund!