MCP for 1C:EDT
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 87%
Response Time: -
First Timer Success: 100%
DitriXNew/EDT-MCP has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DitriXNew/EDT-MCP 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 64.9 places DitriXNew/EDT-MCP in the A tier.
The external contributor pull request merge rate for DitriXNew/EDT-MCP is 87.0%, based on public PR activity from non-core contributors.
DitriXNew/EDT-MCP does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in DitriXNew/EDT-MCP. Reviews community pull requests with focus on project quality.
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/DitriXNew/EDT-MCP?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (39% approval). Keep your diff compact for rapid review.
Ну и совсем шикарно будет кнопку для выбора папки и создания/обновления в ней конфигов ИИ агентов, чтобы не приходилось в каждом отдельно искать и прописывать адрес сервиса. Например у агента OpenCode это делается только в конфиг файле и даже GUI для этого нет. { "$schema": "https://opencode.ai/config.json", "mcp": { "EDT.MCP": { "type": "remote", "url":"http://localhost:8765/mcp", "enabled": true, } } }
Чего не хватает Наш писатель макетов utils/SpreadsheetTemplateWriter.java умеет из форматирования ячеек только три вещи: wrap (строка 110), columnWidths (97) и rowHeights (98). Три свойства, которые в реальных печатных формах нужны постоянно, задать нечем: нужно что в модели платформы поворот текста BaseFormattingCellProperties.setTextOrientation(int) (есть также isSetTextOrientation() / unsetTextOrientation()) автоподбор ширины колонки Format.setAutoWidthCalculation(boolean) вес доли ширины при распределении Format.setWidthWeightFactor(int) Все три — в пакете com._1c.g5.v8.dt.moxel, проверены по индексу Javadoc EDT 2025.2. Попутно в том же Format лежат ещё два, которых у
Надо бы как-то разобраться с длинными тире. С буквами Ё вроде разобрались, а вот с другими символами нет. Надо по аналогии с буками Ё сделать тоже самое. Есть такой стандарт https://1c-syntax.github.io/bsl-language-server/diagnostics/InvalidCharacterInFile/ Который запрещает использовать Среднее тире Цифровое тире Длинное тире Горизонтальная линия "Неправильный" минус Мягкий перенос Неразрывный пробел
Текущая ситуация Папка checks/ не включена в сборку плагина. Она лежит в корне репозитория отдельно от папки mcp/, где происходит вся сборка. В финальный ZIP-артефакт (MCP-EDT.v1.22.1.zip) эти файлы не попадают. То есть пользователь: Устанавливает плагин Должен откуда-то отдельно взять папку checks/ Вручную прописать путь к ней в настройках Почему это неудобно Пользователь может вообще не знать, что такая папка существует Нужно отдельно скачивать/клонировать репозиторий ради markdown-файлов Лишний шаг настройки, который легко пропустить Без этой настройки get_check
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 DitriXNew/EDT-MCP, 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 DitriXNew/EDT-MCP acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.0% were successfully merged into the primary branch.
DitriXNew/EDT-MCP has a recorded first-timer success rate of 100.0%. 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 64.9 places DitriXNew/EDT-MCP in the Welcoming tier.
The external pull request merge rate is 87.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
DitriXNew/EDT-MCP does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for DitriXNew/EDT-MCP 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.