Sources

and integrating Matter. Using topic modeling and qualitative analysis, we identify four recurring areas of concern—Testing, Interoperability, Development, and Platform & Network—and describe how they manifest in the evolution of the codebase and tooling. The findings reveal systematic technical and integration challenges and point to concrete opportunities to refine Matter’s … reflect real-world challenges encountered by both professional developers and hobbyists working across diverse application domains [54], including integration challenges and specifica- tion gaps. By analyzing and categorizing these discussions, we identify the most prevalent technical and usability issues, reveal temporal patterns in problem persistence and resolution, and highlight areas where the Matter specification or its sup- … closely with CI/CD pipelines, enabling projects to evolve through iterative, peer-reviewed changes. Prior work shows that GitHub Issues discussions often capture both technical and socio-technical concerns, such as documentation gaps, environment error, and development bugs [60], [44], [4]. For large and evolving projects, the issue … sues underline the difficulty of keeping dependencies aligned across the many platforms that participate in the Matter ecosystem. Dependency and Environment Configuration issues involve setup and maintenance of third-party libraries, build tools, and frameworks. Developers report build failures due to missing or incompatible components, misconfigured Python environments (e.g., SSL errors or missing tools), and version … Security and privacy concerns appear throughout the repos- itory. We identified 725 issues (5.57% of all issues) containing security or privacy-related keywords, of which 166 remain open. The earliest unresolved issue dates to February 2021 and discusses unsafe API usage. Most of these issues fall within the Testing category, reflecting the central role of … erability issues suggest a need for clearer cross-vendor guide- lines, richer diagnostics, and more comprehensive reference examples for common deployment scenarios. The consistent security issues in testing and commissioning processes high- light the need for automated and formal validation methods for critical protocol behaviors. Together, these findings show that using developer reported GitHub issues as a valuable feedback … teroperability, with integration and network-related bugs often proving difficult to resolve. Development and platform sup- port also demand ongoing maintenance, and security-relevant problems continue to appear across versions. Taken together, these findings indicate that improving Matter standard requires continued effort in testing infrastructure, clearer guidance for cross-vendor deployments, and more automated validation of critical protocol workflows as the standard continues to evolve. 8

It does break and go down; and GHA are a real pain in the ass. But the basic hosting and PR workflow are fine. amluto 7 days ago ... It's still getting things done, for sure, but no longer pleasant to work with. LexiMax 7 days ago That's the real problem with Github these days. Too much critical information behind throbbers that take their sweet time. I find Codeberg much more responsive, despite being an ocean away and having the occasional anti-AI-scraper screen. markstos 7 days ago ... I can say we get no shortage of issues and feature requests from being on an alternative forge. Indeed, we have plenty!

However, despite their power and widespread use, **GitHub issues** can be challenging for beginners and even experienced developers. Making a single mistake—such as committing to the wrong branch or mishandling a merge conflict—can lead to confusion, downtime, or messy repositories. This article highlights six common **GitHub issues** developers encounter and provides practical solutions to resolve them efficiently. ## TL;DR: ... - Developers often face challenges like committing to the wrong branch, forgetting to … ## Common Issues on GitHub Despite its many advantages, using GitHub can sometimes be challenging, especially for developers new to version control best practices. ... ### 1. Committing to the Wrong Branch One of the most common Git mistakes is realizing that you’ve just committed to the wrong branch. Perhaps you intended to commit your changes to a … ### 6. Local Repo Is Not Updated with the Remote or Vice Versa Sometimes your local repository is out of sync with the remote one. This discrepancy can lead to merge conflicts, missing commits, or outdated code. In other instances, you might have commits that aren’t appearing on GitHub, or changes from collaborators that aren’t showing up in your local environment. So how exactly could you fix this issue, … (for rebasing). This helps avoid conflicts and ensures you’re working with the latest code. - Regularly update your local branch by pulling the latest changes from the remote repository using - **Step 2 – Push your local changes** - Make sure that all your local commits are pushed to GitHub using … . This keeps the remote repository up-to-date and in sync with your work. - Make sure that all your local commits are pushed to GitHub using - **Step 3 – Resolve merge conflict** - If conflicts arise during a merge or rebase, Git will pause the process and highlight the conflicting files. Manually resolve the conflicts, stage the changes, and complete the process with … ## Conclusion

### Body Over the past few months, Github has been getting slower and slower on Safari. It has now reached a point where it is unusable. Displaying any pull request with more than a thousand lines changed or even browsing any file with a thousand or more lines of code is fully broken. What happens: - In Activity Monitor, the rendering process is running at 100%. - Rendering the page is so slow, Safari displays blank space when scrolling up and down. - Any interactive features like search is so slow it doesn't work. - Pull request review is extremely painful (scrolling back and forth is impossible to do quickly, posting comments is extremely slow, even checking the "Viewed" checkbox sometimes takes several seconds, etc.). … ### LeLunZ Aug 25, 2025 ... For bigger PRs I can't edit anything or press on any buttons. Seems like such a big page breaks something? I just tried it from a current branch to a really old version of one of my projects, and there are 403 commits and 855 changed files. In such a case the GitHub UI becomes completely unusable. … ### BrentMifsud Aug 25, 2025 ... Even small PRs I can't do anything. Adding reviewers, adding labels, etc... every action on the page takes many seconds. The page often locks up as well. This wasnt an issue a few weeks ago. - 👍 3 3 replies ... As someone who writes bugs for a living I'm careful to complain. That said, this has become a real pain point for me, personally. It's not uncommon for me to do the following things opening a PR: - Changing the base branch - Writing the description - Toggling the create button between draft and ready to review - Assigning reviewers - Assigning myself I do this several times a day and within the last few weeks the page will lock up *every* time. Sometimes I'll refresh the browser and even that takes a while to perform. Historically I've had no issues with this in Safari. 0 replies … #### lukehefson Aug 28, 2025 ... > This lines up with my experience. Initially the new files experience seemed to improve things, but in the last week, I've noticed the changed files feature is unbelievably sluggish. I can barely scroll through more than a few hundred lines of change, and the page locks up. Yeah it's definitely the files experience. But I've also noticed sluggishness all around the past week or so. For example: In any comment box, when you start to type something that autocompleted (like an @mention), the character rendering slows riiiiight doooooown. … #### uson1x Aug 27, 2025 - Wow I did not know this problem was only in safari. ... It did get faster with latest PR review UI update, but still rather slow right now - 👍 2

Earlier today, GitHub, the cornerstone of modern software development, suffered a significant global outage, leaving millions of developers unable to push or pull code and effectively grinding workflows to a halt. ... Reports of the disruption began surfacing on social media and technical forums like Hacker News, with developers sharing common error messages. Users attempting to interact with repositories via SSH were met with a `fatal: Could not read from remote repository` error. Meanwhile, those using HTTPS connections encountered HTTP 500 internal server errors, indicating a failure deep within GitHub’s backend services. ... This outage does not appear to be an isolated event. Several users noted a perceived increase in the frequency of GitHub service disruptions, with one commenting this was the “5-6th time this month,” citing persistent degradations in the GitHub Actions CI/CD service as a recurring pain point. This pattern raises serious questions about the platform’s stability and the potential for cascading failures in a tightly integrated ecosystem.

#### 📈 Expanding project limits All your issues can also be laid out in a GitHub Project. We've listened to your feedback that you want space for more issues in your projects, so we've expanded the limits from 1,200 to a huge **50,000** items per project! 🎉 With today's general availability announcement, we'll be removing the opt-out option in the coming weeks. Moving forward, we'll also make increased limits your default mode. … #### beberlei May 7, 2025 - This is a real problem, even with projects, because you would don't always group by parent/child in projects, so there are enough views where you would end up with (to keep this example) a list of three or more tickets all named "UI" - - - - … ## GitHub Projects + GitHub Issues Automation Capabilities Automation between GitHub Projects and GitHub Issues feels half-baked. Webhooks make it difficult to fully automate issues/projects ourselves. For example, if I want to automatically update an issue’s label when it's moved from one project field (e.g., “Category”) to another, there’s no webhook available for GitHub Projects. The only workaround is to run scheduled jobs to keep everything in sync — but that’s expensive and inefficient. … ## GitHub Projects View with Mixed Issue Types and Static Project Fields Another challenge arises when using mixed issue types within a single project, each needing different project fields. For example, we might have a field like “Effort,” which only applies to Tasks, not Stories. Or an “Impact Area” field meant for Bugs, but not Features. Since all these issue types live in the same project (to maintain correlation and visibility), having static fields for everything becomes cumbersome and semantically unclear. … ### SeeringPhil May 23, 2025 - Hello there! Great work with the new issues/subissues and projects view 😄 There are some pain points when using those new features: … - Once devs fix those issues, they can then add the sub-issue ticket in QA project/backlog. That's how it used to work before too, but not anymore. We're concerned about it as we've setup an integration of QA project with our slack channel specifically for QA related alerts. So whenever a new sub-issue is added with main ticket, an alert is sent by default because the by default selected projects are both i.e. main project and QA project.

Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.

- Why is Github very slow and unresponsive? This occurs when visiting any page in the gh.com UI as well as when trying to git pull from terminal (macOS). There seems something terribly wrong with the UI lately. A request on the same URL can be fast one time, but when refreshed it can take ages while resulting in a timeout. Then after another refresh it can take a long time to complete just before the timeout, resulting in a success When is this going to be resolved? ... - I have noticed that the GitHub website has been slow and annoying to navigate since ~Thursday, 17 April, 2025. There is a significant delay (1/2 seconds) after I click somewhere and it displays the codes. I have no issues with committing my projects, though. CLI is fine. It's just the website navigation. … ### mekedron May 28, 2025 ... I have exactly same issue as @phazarik - everything else is OK but not the website. Recently, I migrated my repos from Bitbucket to GitHub. And yes, I got shocked when I realize how GitHub's web interface is slow. It takes 2-3 seconds each click to wait till the page load. I tried different computers, connections, VPNs, but nothing works. However, I noticed that in Google Chrome GitHub works fine, however, the problems I experience are in Firefox only. @ghostinhershell unfortunately I still experience slow interface. And I never use Github anonymously, so I don't believe this is a problem I experience. However, I could significantly improve the experience by disabling "turbo links" with this small user script:

GitHub added 36 million developers in 2025—roughly one new account every second—but the platform's latest analysis suggests this explosive growth is creating serious sustainability problems for open source projects worldwide. The February 18 report from GitHub's Octoverse team highlights a widening gap between contributors and maintainers, compounded by what the industry now calls "AI slop"—low-quality, auto-generated pull requests that consume maintainer time without adding value. … ## The AI Problem Nobody Wanted While AI tools lowered barriers for new developers, they've simultaneously created a flood of problematic contributions. Maintainers report that review time has increased faster than the number of people available to do reviews—some describe it as "a denial of service attack on human attention." The platform saw nearly 1 billion commits in 2025, up 25% year-over-year, with 43.2 million pull requests merged monthly. That volume becomes unmanageable when a significant portion requires extensive rework or outright rejection. Some maintainers have started using AI defensively—triaging issues, detecting duplicates, and handling routine labeling. GitHub has released new tools to help, though the report acknowledges these are stopgap measures. … ## The Maintainer Crisis Record growth looks great on paper. In practice, it's straining the relatively small group of people who actually maintain critical infrastructure. The report recommends clear paths from contributor to reviewer to maintainer, shared governance models spanning multiple timezones, and documentation that doesn't assume prior knowledge. "The important question going forward isn't how much it will grow," the analysis concludes. ... Projects that fail to invest in organizational maturity risk stalling entirely—or accumulating technical debt that eventually becomes insurmountable. For an ecosystem that underpins most of the world's software, that's not a theoretical concern.

# GitHub’s August 2025 Performance Woes: A Wake-Up Call for Dev Infrastructure GitHub just hit a major infrastructure wall—and developers are feeling the pain. Performance Plummets During Critical Development Cycle The platform's August slowdown couldn't have come at a worse time. While traditional finance was busy chasing 0.05% yield optimizations, GitHub's latency spikes were costing developers real productivity. Response times lagged, pull requests stalled, and CI/CD pipelines choked—all while VCs were probably writing checks for another 'disruptive' project management tool. Infrastructure Strain Exposes Centralization Risks Single points of failure aren't just a crypto concern anymore. ... In August 2025, GitHub encountered three critical incidents that led to degraded performance across its services, as reported by GitHub. These incidents highlighted areas for improvement in the platform's infrastructure and monitoring systems. ## August 5 Incident The first incident occurred on August 5, lasting 32 minutes, due to a production database migration error. The migration aimed to drop an unused column from a table supporting pull request functionality. However, the Object-Relational Mapping (ORM) system still referenced this column, resulting in elevated error rates affecting pushes, webhooks, notifications, and pull requests. Approximately 4% of web and REST API traffic was impacted. The issue was initially mitigated by instructing the ORM to ignore the removed column, but a secondary incident affected around 0.1% of pull request traffic. GitHub plans to enhance automation and safeguards to prevent similar issues in the future. ## August 12 Incident On August 12, a more prolonged outage occurred when GitHub's search functionality was degraded for over three hours. Users experienced issues such as inaccurate search results and failures to load certain pages. The incident was traced back to connectivity problems between load balancers and search hosts, which were exacerbated by retry queues overwhelming the load balancers. This led to a peak failure of 75% of search queries. The issue was resolved by throttling the search indexing pipeline and rebooting a search host, which restored connectivity. ## August 27 Incident The final incident on August 27, lasting 46 minutes, saw Copilot and other services experience degraded performance. Similar to the first incident, it was caused by a database migration error where a column drop led to 5xx responses. GitHub has since blocked all drop column operations as a temporary measure and is working on implementing graceful degradation to ensure Copilot issues do not impact other services.

Artificial intelligence sits at the center of 2025's open source story, but not only in the flattering ways the industry tends to celebrate. AI has made it easier for new developers. They can now understand codebases, draft patches, and contribute sooner. But this comes with a downside. Maintainers face a flood of what the report calls "AI slop." This means high-volume, low-quality, and often inaccurate contributions. These contributions take up reviewers’ time without significantly helping the project. The scale of this problem is significant enough that GitHub draws an analogy to a denial-of-service attack on human attention. Auto-generated issues and pull requests have increased dramatically, but the number of maintainers with the authority and context to review them has not kept pace. The review burden has grown faster than the reviewer pool, creating a bottleneck that threatens to stall projects even as their contributor counts climb. … Growth at the bottom of the contributor funnel has not been matched by equivalent growth in people moving into ownership and maintainer roles. The report highlights a growing gap. More people are joining open source projects, but the number taking on stewardship roles remains steady. This gap creates problems. As more developers join, they bring onboarding questions, duplicate issues, and uncertainty about community norms. Existing maintainers have to deal with all this. … GitHub's 2026 outlook highlights that the open source community faces not just technical challenges, but mainly organizational ones. The tooling to write software has never been more accessible. The missing layer is governance, documentation, and community support. These are needed to manage what happens when millions of new contributors join without a shared context.

## 66% of developers are frustrated with AI solutions that are almost right The biggest single frustration, cited by 66% of developers, is dealing with "AI solutions that are almost right, but not quite," which often leads to the second-biggest frustration: "Debugging AI-generated code is more time-consuming" (45%) Technology → Admired and Desired … ## Privacy, pricing and better alternatives are top reasons developers turn their back on a technology |Detraction|Overall Rank|Median Rank|Mode Rank| |--|--|--|--| |Security or privacy concerns|1|3|1| |Prohibitive pricing|2|4|1| |Availability of better alternatives|3|4|1| |Poor usability|4|4|4| |Inefficient or time-costly|5|5|5| |Outdated or obsolete technology or features|6|5|8| |Ethical concerns|7|6|8| |Lack of or sub-par API|8|6|8| |Lack of AI or AI agents|9|9|9| |Other|10|10|10| The reasons to reject a technology are nearly universal. The top three deal-breakers for all developers are security or privacy concerns (Rank 1), prohibitive pricing (Rank 2), and the availability of better alternatives (Rank 3). The lack of AI is the least important factor (Rank 9). Technology → Worked with vs. want to work with ... ## More developers actively distrust the accuracy of AI tools than trust it More developers actively distrust the accuracy of AI tools (46%) than trust it (33%), and only a fraction (3%) report "highly trusting" the output. Experienced developers are the most cautious, with the lowest "highly trust" rate (2.6%) and the highest "highly distrust" rate (20%), indicating a widespread need for human verification for those in roles with accountability.