Suggest Unpacking the Latest Version Files to a New Branch to Enhance Developer Experience and Enable GitHub Features

[fredgan]

Problem Description:

Currently, all historical release ZIP files are stored in different directories. This approach is not developer-friendly because it leads to the following issues:

• Inability to Intuitively See the Latest Code: Developers cannot directly view the most recent code files in the repository's main view, making it difficult to quickly understand the current state of the project.
• Inability to Review Code and Submit Pull Requests: Since the latest code is not in a standard branch, developers cannot perform code reviews, suggest changes, or submit Pull Requests in the usual workflow.
• Difficulty in Comparing Differences Between Releases: Comparing two different releases to understand new features or changes is cumbersome, requiring downloading and manually comparing ZIP files.
• GitHub Security Scan (SAST) Cannot Function Properly: The security scan feature (Static Application Security Testing) provided by GitHub cannot effectively analyze the code under this directory storage mode.
• GitHub Actions (CI/CD) Cannot Be Used: The lack of a standard branch containing the latest code prevents the utilization of GitHub Actions for continuous integration and other automation processes.

Proposed Solution:

To address the aforementioned problems and enhance the developer experience, we suggest unpacking the files from the latest version's ZIP file into a new branch.

Benefits of the Proposed Solution:

• Intuitive Access to the Latest Code: Developers can easily view and work with the most recent codebase directly within the repository.
• Enabled Code Review and Pull Request Functionality: Standard development workflows for code review and Pull Request submission will be enabled.
• Simplified Release Comparison: Comparing differences between releases will be much easier using GitHub's comparison tools.
• Enabled GitHub Security Scan: GitHub's security scan feature will be able to analyze the latest code, improving code security.
• Usability of GitHub Actions: GitHub Actions can be configured for automated builds, tests, deployments, etc., enhancing development efficiency.

Specific Recommendation:

Create a new branch, for example, named latest or release-latest, and unpack the contents of the most recent release ZIP file into this branch.

[fredgan]

Another way, we can see the license easily

[fredgan]

@michaelhkay Hi, can you have a look at this issue?

[ndw]

There is certainly room for improvement here. This repository has initially been setup to mirror what used to be published on SourceForge. We'll see about improving it as quickly as is practical.

[fredgan]

There is certainly room for improvement here. This repository has initially been setup to mirror what used to be published on SourceForge. We'll see about improving it as quickly as is practical.

Hi, @ndw I noticed that you have uploaded two new versions. Has any progress currently about this?

[ndw]

Not yet, I'm afraid. But it's on my list.

[JohnWick5-ZZD]

@ndw Looking forward to improving this repository for github developer. Thx a lot : )

[ruv]

The idea is that there is no need to put the archives under version control (i.e., into the GitHub Git repository). It is enough to put them in the Releases section.

Note that «Source code (zip)» (as well as tar.gz) is automatically added into the Assets of a release. This file contains a snapshot of the source codes. Due to abuse of the Git repository, this file currently contains archives for all previous versions (which are placed under version control as archives).

Screenshot of Assets example

_{(tap/click to unfold)}