多脚本多配置统一管理与自动化工具 | 轻松管理大量脚本并存储多个用户配置、设计自动化任务流、监看脚本日志，大幅提高自动化代理效率与稳定性！
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 10%
Response Time: -
First Timer Success: 9%
AUTO-MAS-Project/AUTO-MAS has a recorded first-timer success rate of 9.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AUTO-MAS-Project/AUTO-MAS respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.5 places AUTO-MAS-Project/AUTO-MAS in the A tier.
The external contributor pull request merge rate for AUTO-MAS-Project/AUTO-MAS is 9.8%, based on public PR activity from non-core contributors.
AUTO-MAS-Project/AUTO-MAS currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in AUTO-MAS-Project/AUTO-MAS. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in AUTO-MAS-Project/AUTO-MAS focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/AUTO-MAS-Project/AUTO-MAS?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (12% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
在提问之前... 我确认这是需求建议，而不是 Bug 反馈 我已搜索过活跃议题与已关闭议题，确认该需求未被提出过 需求描述 MAS 版本号变化时，自动把数据备份到用户指定的目录： 在设置里选好备份目录（建议放在安装目录外）后开启；备份内容与现有「导出数据备份」（#434）相同。 只写不读：不自动恢复，不碰源数据。清理时只删自己生成的备份文件（按文件名规则识别），目录里的其他文件一律不动。新备份写完后才清理旧的，写失败就不删任何文件。 保留规则：按备份时旧版本号的前两位 主.次 分段（beta 也算在同一段，5.6.0-beta.1 属于 5.6）。 升到 X.Y 时只留 X.Y 本段和上一段，更早的删掉：升到 5.6 时删 5.4.x，5.5.x 留到升 5.7 时再删。 「上一段」按 (主, 次) 取现有备份里比当前段小的最大那一段，不拿次版本号减一：升到 6.0 时上一段
当前已经实现在调度台选择某队列启动时可以选择某一脚本开始启动，希望在选择某脚本的情况下可以选择从某一用户开始启动 ui可以复用从某一脚本开始启动的ui，当选择的是队列时，右侧区域可以选择从某一脚本开始，当选择的是用户时，该区域可以选择从某一用户开始
背景 脚本设置会把各用户的配置存到按 UUID 区分的目录。编辑页只能拉起配置程序，无法一键打开对应文件夹，手动找路径很麻烦。 期望 在用户编辑页（已有 userId 时）增加「打开配置文件夹」 点击后在系统文件管理器中打开该用户的配置目录 目录尚不存在时自动创建再打开 覆盖通用 / MAA / SRC / MaaEnd 等脚本类型的用户编辑页
有的游戏更新了以后当天可能需要手打，专门去修改队列又有点麻烦
严重的问题 缺少拖拽提示 这个列表支持拖拽排序，但是视觉上完全看不出来。用户只有把光标移上去后，光标改变，才会意识到这里可以拖拽。 这里更混乱了，外层卡片列表可拖拽，内层子列表也可拖拽，而且都没有任何提示。 一般情况下会在 list item 的最左侧加上图标，暗示用户这里可以拖拽。 例如 可拖拽区域过宽 目前整个 item 都会触发拖拽行为。即便用户点击是的 item 上的一个可交互元素，也会触发整个 item 的拖动动画。 更合理的设计应该是加上前面的拖拽图标后，仅允许图标以及周围一部分区域触发拖拽行为。 不严重的问题 以下是个人偏好比较强的观点，不喜可跳过。 1 无用 Tooltip 图标和按钮文本的含义已经足够明确了。 2 无用 Toast Toggle 按钮本身的状态就足够提示当前是否开启了。除非出错，否则没必要提示。 而且
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to AUTO-MAS-Project/AUTO-MAS, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of AUTO-MAS-Project/AUTO-MAS acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 9.8% were successfully merged into the primary branch.
AUTO-MAS-Project/AUTO-MAS has a recorded first-timer success rate of 9.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.5 places AUTO-MAS-Project/AUTO-MAS in the Welcoming tier.
The external pull request merge rate is 9.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AUTO-MAS-Project/AUTO-MAS currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AUTO-MAS-Project/AUTO-MAS are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.