WEEK OF 2025/09/19 - The Funkin' GitHub: Our Evolution Since Weekend 1

11 minute read - Published on: 2025/09/19

Table of Contents

Hey funkBlog fans,

I’m Hundrec, the new Production Manager for the Funkin’ Crew. Nice to meet you!

As Abnormal recounted, we went through quite the journey to join the Crew. Back in March, I wrote a blog to share a few stories about the fun stuff we encountered as GitHub moderators.

So let’s take a journey into the distant past, when 0.5.3 was the latest version and the Pit Stop 2 trailer just dropped, and explore the Funkin’ GitHub!

T i m e t r a v e l t r a n s i t i o n

With the Pit Stop 2 update right around the corner, the contributors over at the Funkin’ GitHub repository have been real busy making the game better for you!

As a moderator for the repo, I’m excited to show you the ins and outs of our fun little community, and how you (yes, you!) can contribute to the development of the game!

What is the Funkin’ GitHub?

The Funkin' GitHub repository is the go-to place for reporting bugs and crashes, suggesting cool new features, and even contributing your own code to the game!

It’s also where all the game’s code is publicly stored, ready to be downloaded and compiled into your very own copy of Friday Night Funkin’ (hooray for open source!).

Although the repo has always been a fun place for bug-hunters and programmers, it hasn’t always been well-organized or easy to use. Since the release of the Weekend 1 update, the repo has gone through some huge changes.

Mounting Problems

It was May 9th, 2024.

Weekend 1 had been out for just over a week, and new issues were flooding in. Players were discovering a plethora of bugs and crashes from Null Object Reference to Pico gone missing. Lots of people were asking for help compiling the new v0.3.2 source code. Some issues were even reported multiple times!

Compiling errors, coming in hot!

There were other glaring issues throughout the repo too. The bug report template was difficult to fill out, issues weren’t being reviewed and labeled, the README linked to a non-existent Contributor’s Guide…

The disorganization was getting out of hand. At this rate, the game’s programmers ninja_muffin99 and EliteMasterEric would have to spend more time sorting through hundreds of issues than fixing game-breaking bugs!

Fortunately, contributors from the Funkin’ GitHub community offered to help. Let’s take a look through some of the contributions that have made the repo as organized and user-friendly as it is today!

Issue Templates

When you report a bug or suggest a feature, you fill out an “issue template” with important information (e.g. game version, platform) that helps the developers understand your issue.

Back when Weekend 1 first released, our issue templates looked awful. They were overloaded with text, contained many spelling mistakes, and often confused users who just wanted to report a capital H.

Well, it’s got personality (much love to Cam!)

Even worse, all of the template’s instructions would be visible after submitting the issue. This led to a lot of visual clutter and made it harder for the developers to review the growing backlog of active issues.

Thankfully, all of these problems were solved when community member tposejank introduced fancy new templates complete with clear instructions, a pre-submission checklist, and neat little dropdown menus!

Crystal clear!

Since then, the community has enjoyed a more streamlined and intuitive reporting experience. The submission instructions tell you exactly what to do and why you should do it, the checklist ensures the uniqueness and clarity of your issue, the dropdowns show you exactly what your options are, and the text fields are specifically tailored to each issue template. Huge upgrade!

The Moderation Team

Throughout 2024, Eric did the heavy lifting in the repo. He would add labels to categorize posts, reply to issues, review pull requests (code contributions), accidentally close them all, and clean up duplicate reports.

Jokes aside, it was incredibly difficult for one person to manage over 600 issues and 100+ pull requests, all while programming features for the next big update. That’s why, on January 21st, Eric invited AbnormalPoof and myself to become moderators for the Funkin’ GitHub repository (Eric’s announcement). With two people dedicated to cleaning up and maintaining issues and pull requests, Eric was finally free to focus on making the game!

Since Day 1, AbnormalPoof and I have worked hard to organize and revamp the whole repository. In less than two weeks, we managed to close over 200 resolved and duplicate issues, bringing the total number of open issues from 600+ down to 458! And while that’s still a whole boatload, we’ve been actively managing new issues to ensure that number doesn’t break any records again.

GitHub’s activity summary for January… we cleaned up big time!

On top of that, we’ve collaborated with Eric to carry out a project I’m very proud of to this day…

The GitHub Label Cleanup Proposal

Labels are important. Our repo uses them to categorize issues and pull requests (PRs, for short) by their status, type, topic, and other information.
For example, an issue/PR labeled status: pending triage hasn’t been reviewed, while an issue/PR labeled status: rejected won’t be added to the game.

Over the course of 2024, there was a growing labeling problem. Many issues had incorrect labels or no labels at all, the labels themselves were cluttered and inconsistent, and we had a bot running around marking things as “potential duplicate” (it was wrong every time).

That’s why I opened The GitHub Label Cleanup Proposal, which detailed exactly how to clean up and organize the labels. Delete some here, create some there, group these together, change those colors, etc. etc.

It was a lot!

After some discussion and revision, Eric implemented all of the changes from the proposal.

Our Labels list before vs. after the Label Cleanup Proposal

The difference was night and day: the new labels were neatly categorized, colored consistently, and clearly defined. My favorite feature is the use of green and red to color labels indicating completion. You can now easily tell apart which issues are status: resolved (green) and which ones are status: rejected (red). How convenient!

With these huge changes, AbnormalPoof and I have made sure to label every issue and PR created since Weekend 1 released (almost 2000 in total). No more mystery issues :)

Contributing Guide

Many GitHub repos have a Contributing Guide to help new contributors learn the rules before opening their first issue or PR.

For the longest time, our Contributing Guide looked like this:

This wasn’t too big of a deal on its own, but the README introduction to the repo actually linked people to this guide. While this was pretty funny, it would have been nice to have an official resource for learning how to contribute to the development of the game.

Last month, AbnormalPoof and I got together to create just that. With feedback from Eric and the community, we made sure to cover everything you should know before making your first contribution. Check out our brand new Contributing Guide to find out how you can make an impact on Friday Night Funkin’!

Oh, and I’m happy to report that the link in the README finally works :)

Wrap-up

I hope you enjoyed reading about the history of the Funkin’ GitHub repo. I had a lot of fun writing about it!

You (that’s right, you!) are always welcome to drop by and contribute, so feel free to join the community. Whether you’re reporting bugs, suggesting new features, fixing a typo, or adding an entire Stage Editor (shoutout to KoloInDaCrib!), there’s something there for everyone!

Thanks for reading, and I hope to see you on the Funkin’ GitHub :)
Hundrec 💯

Hey!

Hey!

Oh good, you’re finally awake. You’ve been mumbling about duplicate issues and Null Object Reference this whole time.
I realized that I didn’t get a chance to tell you about what I do for the Crew now, so I’ll save that for another blog (or four).

For now, here’s a fun fact: Friday Night Funkin’ now has two independent streams of development!
While the main programmers work on fresh new features for upcoming updates, the rest of us bring in bugfixes and optimizations from our contributors at the Funkin’ GitHub. So when we release new patches, rest assured that the next update is still on track.

Speaking of patches, we just released the 0.7.5 update!
Here’s one change I love: GitHub contributors NotHyper-474 and KoloInDaCrib ironed out every lagspike in Stress (Pico Mix) for a buttery smooth disgusting orange boy experience.

Check out the latest fixes in the Changelog and mobile store Release Notes!

But before you go grab the update, here’s a legendary song to sing along to:

See ya next time!
Hundrec 💯