Using GitHub Actions is a popular choice as it is easy to deploy and eliminates the effort to manually upload assets. In addition, it provides a normalized platform to build programs and guaranteed the accessibility for everyone to build the program as long as they follow the workflow file.
I personally encountered many problems while building qETRC on Windows, and so I really hope that the program could use Actions.
On the revision number part, the current major-minor-fix naming system is enough and adding an extra build revision number only increases the cost of normalizing real reason is that I fount it hard to be manipulated to be a scoop manifest file
Using GitHub Actions is a popular choice as it is easy to deploy and eliminates the effort to manually upload assets. In addition, it provides a normalized platform to build programs and guaranteed the accessibility for everyone to build the program as long as they follow the workflow file.
I personally encountered many problems while building qETRC on Windows, and so I really hope that the program could use Actions.
On the revision number part, the current
major-minor-fixnaming system is enough and adding an extra build revision number only increases the cost of normalizingreal reason is that I fount it hard to be manipulated to be a scoop manifest file使用 GitHub Actions 是一种流行的选择，因为它易于部署，并且省去了手动上传资产的工作量。此外，它提供了一个规范化的平台来构建程序，并保证了只要遵循工作流文件，每个人都可以构建程序。
我个人在 Windows 上构建 qETRC 时遇到了很多问题，所以我真的希望该程序可以使用 Actions。
在修订号部分，当前的
major-minor-fix命名系统已经足够了，添加额外的构建修订号只会增加规范化的成本真正的原因是我发现它很难被操纵为 scoop 清单文件中文是机翻，懒得写了（