eyalgolan/statecraft-israel - Open Source PR Review Scorecard

A Civilization-style strategy game about governing Israel from 15 May 1948. Real ministers, real map, every fact sourced. Unity + deterministic C# sim.

C-Rank Grade: D (Risky) - 19/100

External PR Merge Rate: -

Response Time: -

First Timer Success: -

Frequently Asked Questions

Is eyalgolan/statecraft-israel welcoming to first-time open-source contributors?

eyalgolan/statecraft-israel has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in eyalgolan/statecraft-israel 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.

What does the 19.5 C-Rank™ score (D Tier) represent?

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 19.5 places eyalgolan/statecraft-israel in the D tier.

What is the external contributor pull request merge rate for eyalgolan/statecraft-israel?

The external contributor pull request merge rate for eyalgolan/statecraft-israel is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in eyalgolan/statecraft-israel?

eyalgolan/statecraft-israel currently has 33 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

eyalgolan
eyalgolan/statecraft-israelD•Risky266
GitHub
Back to Explorer
eyalgolan

eyalgolan/statecraft-israel

266
InactiveD•Risky(19/100)Low Sample (<20 PRs)C#

A Civilization-style strategy game about governing Israel from 15 May 1948. Real ministers, real map, every fact sourced. Unity + deterministic C# sim.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.5/10
Patience Score
8.0/10
Nitpick Rate
40%

Strict review standards in eyalgolan/statecraft-israel. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in eyalgolan/statecraft-israel focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Update docs or README when behavior changes
  • •Keep PRs small and focused on one change

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not ship user-facing changes without matching docs
  • •Do not mix unrelated refactors with feature work
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for eyalgolan/statecraft-israel
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/eyalgolan/statecraft-israel)](https://getmerged.abhishekco.de/eyalgolan/statecraft-israel?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

What problem does this solve The Hebrew UI preview (?lang=he, #193) has all its interface text in unity/Assets/UI/strings.he.yaml. It was written by the maintainers with AI help and has not been read by a native Hebrew speaker as a whole. A careful read catches unnatural wording, wrong gender agreement and inconsistent terms before more players see it. What you propose A native Hebrew speaker reads strings.he.yaml against strings.en.yaml, line by line, and suggests fixes. How to start (no setup needed): Open unity/Assets/UI/strings.he.yaml and unity/Assets/UI/strings.en.yaml side by side on GitHub. Each key has the same name in both files. For any line that reads badly, post a comment here with: the key, the current Hebrew, your suggested Hebrew, and one line on why. Keep {0}-style placeholders exactly as they are. Already decided, please keep: ביטחון for both the Security meter and the Defence screen; כישורים; המצב הביטחוני; מנדטים (Knesset) / חברי

📅 Opened Oct 14, 2026💬 0 comments
Quality: 90/100Contribute

What problem does this solve The player golden workflow (player-golden.yml, #533) checks the macOS player's x86_64 slice on GitHub's macos-15-intel runner. GitHub's runner-images team says that image is "available from now until August 2027. This will be the last available x86_64 image from Actions" (actions/runner-images#13045, 19 September 2025). Once it is retired, the x86_64 slice of the Universal Mac build would ship unchecked. What you propose Before August 2027, decide how the x86_64 slice is checked once macos-15-intel is gone: run it under Rosetta on an arm64 runner (arch -x86_64; the arm64 images install Rosetta); or a self-hosted Intel Mac; or drop x86_64 from the Mac build, if Unity and the player base allow. Done when the workflow no longer depends on macos-15-intel, and a test pins the replacement. Refs #533. Needs Unity? No: the workflow and tools/player_golden_check.py only.

📅 Opened Oct 14, 2026💬 1 comment
Quality: 90/100Contribute

content/events/bernadotte_assassination.yaml, line 14 (a YAML comment, not text the player sees), says "About 200 Lehi members were arrested". The figures cited in the same comment add up to more than that: Ben-Gurion to the Provisional State Council: 184 in Jerusalem and 62 in the Tel Aviv district, 246 in all (also lines 54-55 of the file); UN document S/1315: 184 in Jerusalem and 82 in Tel Aviv and other parts of the country by 23 September, 266 in all (lines 88-89); JTA: "hundreds", with 200 moved to Jaffa. To do: reword the comment so it states the sourced counts rather than "about 200". For example: "About 250 Lehi members were arrested (Ben-Gurion: 246; S/1315: 266 by 23 September; JTA: hundreds, 200 moved to Jaffa)". Comment only. No card text, effect, golden or sources: change, and no CHANGELOG line, since the comment is not player-visible. Check that dotnet test sim/Statecraft.sln still passes. Good first issue: one line in one file, with the sources already in the file.

📅 Opened Oct 14, 2026💬 0 comments
Quality: 90/100Contribute

What: towns round 2 (#31, branch promo-towns-2) draws Jerusalem's Old City as a symbolic walled square 4 km across, about 4 times the real one (0.9 km^2), so the walls hold the Haram and a quarter of houses at the kits' scale. The drawn 1948 roads (300 m ribbons) meet by Jaffa Gate and loop round the north and east. At this size they cross inside the square, through gaps in the walls, and that causes three departures from the real city: the walls have gaps wherever a road crosses, and each gap is drawn as a gate, so the census counts 13 gates (the real walls have seven open gates and the sealed Golden Gate); the Haram's platform is wider than long (1.3 x 1.1 km; the real one is about 488 x 315 m, long north-south), because only one place in the south-east quadrant is clear of every route; Al-Aqsa stands in the platform's south-east corner, not across its south end, and the citadel is moved east off the drawn Hebron road. Done when: The 1948 roads near the Old City run round the wall

📅 Opened Oct 12, 2026💬 0 comments
Quality: 90/100Contribute

Status (2026-10-14): the derived rule is done (#302) and no hex is mislabelled under it; #401 has merged. Left: the info-panel note naming a town in a neighbouring water hex (Tiberias). Whether 25 km is the right threshold is a design question with the owner. The integration play-through found that the Tiberias hex reads "Coastal plain · elevation 70 m". Tiberias stands on the shore of the Sea of Galilee, at about −200 m. What happens Which hex Tiberias lands on: Tiberias (35.5333 E, 32.7944 N) falls in the lake hex q11 r8, which is at −214.5 m and is a lake. So tools/hexgrid.py moves it to the nearest land hex, q10 r8. That hex's centre (35.476 E, 32.807 N) is on the slopes west of the lake, at 70.4 m. The elevation shown is that hex centre's, which is correct for the hex. The wrong label: classify() in tools/hexgrid.py gives every land hex with a median of 0–200 m and enough rain the fallback biome coastal_plain (rule 7, "everything else"). So inland lowlands far from the sea

📅 Opened Oct 11, 2026💬 3 comments
Quality: 90/100Contribute
Looking for more C# beginner tasks?Explore C# GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for eyalgolan/statecraft-israel

When evaluating whether to contribute to eyalgolan/statecraft-israel, 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 eyalgolan/statecraft-israel acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to eyalgolan/statecraft-israel

01

Is eyalgolan/statecraft-israel welcoming to first-time open-source contributors?

eyalgolan/statecraft-israel has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 19.5 C-Rank™ score represent?

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 19.5 places eyalgolan/statecraft-israel in the Risky tier.

04

What is the external contributor pull request merge rate for eyalgolan/statecraft-israel?

The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in eyalgolan/statecraft-israel?

Yes, eyalgolan/statecraft-israel currently has 33 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for eyalgolan/statecraft-israel 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.