Weekly GitHub Report for FGA

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v3030

1.2 Version Information:

The version released on May 25, 2026, includes key updates such as improved GitHub workflows using commit SHA, an upgrade of Gradle to version 9.5.1, and expanded support features. These changes enhance development efficiency and broaden the app’s compatibility.

Click here to view the full release notes!

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. Custom Game Area (black bars) megathread: This issue is a megathread dedicated to automatically calculating Custom Game Area values for devices that display black bars when playing Fate/Grand Order, helping users adjust offsets to ensure proper screen interaction. It provides instructions on how to identify if black bars are present, how to post screenshots for offset calculation, and notes that many devices no longer require manual adjustments due to recent updates and system settings.
   • The comment section consists mainly of users posting screenshots of their devices with black bars and requesting offset values, while maintainers and community members provide specific offset recommendations, troubleshooting tips, and advice on proper screenshot submission; many users report success after applying suggested offsets or adjusting system settings, though some continue to face issues due to overlapping UI elements or recent game updates affecting detection.
   • Number of comments this week: 1

Since there were fewer than 5 open issues, all of the open issues have been listed above.

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 1

Summarized Issues:

• Auto Leveling Feature Bug: The recent servant enhancement UI update on the KR server has caused the auto leveling feature to stop working, indicating a compatibility issue between the new UI and the automation system. This problem prevents users from utilizing the auto leveling functionality effectively.
• issues/2243

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 2

Summarized Issues:

• Support Selection Bug: The support selection system incorrectly identifies and selects the wrong servant, specifically choosing Alice Mahoyo as Skadi when only Skadi is selected for farming support. This causes confusion and inefficiency in gameplay as the intended support is not properly utilized.
• issues/2144

• Server-Specific Feature Breakage: After an update, the servant enhancement feature stopped working on the Korean servers due to changes related to the auto add ember update. This update caused the functionality to break specifically for the Fate-Grand-Automata application on that server, impacting user experience.
• issues/2194

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 0

As of our latest update, there are no open pull requests for the project this week.

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 0

As of our latest update, there are no closed pull requests for the project this week.

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

As of our last update, there are no open or closed pull requests with discussions going on within the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.