Skip to content

feat: sync GameDB Steam presets directly - #10

Merged
ReenigneArcher merged 3 commits into
masterfrom
feat/sync-gamedb-steam
Sep 24, 2026
Merged

ReenigneArcher merged 3 commits into
masterfrom
feat/sync-gamedb-steam

Conversation

@ReenigneArcher

Copy link
Copy Markdown
Member

Description

  • Import PC games with one unambiguous Steam external ID from GameDB's published gh-pages branch directly into PresetDB's database branch.
  • Commit and push each changed game JSON file separately. Skip unchanged files, retry database branch races, and let the next daily run continue after a timeout.
  • Keep issue-backed preset IDs numeric and their launch values contributor-managed. Direct imports use the stable steam ID, have no issue provenance, and cannot be replaced through an issue.
  • Run daily at 07:00 UTC, using the standard checkout action and the GitHub job timeout. Dispatch one Pages build when any files were published.
  • Bound concurrent ProtonDB lookups during Pages builds as the Steam catalog grows.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

See our AI usage policy.

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

Comment thread src/gamedb-sync.js Fixed
@codecov

codecov Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 96.79144% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.45%. Comparing base (fcd035a) to head (7191c6f).
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
src/gamedb-sync.js 95.89% 6 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
+ Coverage   88.51%   89.45%   +0.94%     
==========================================
  Files          13       14       +1     
  Lines        1306     1480     +174     
==========================================
+ Hits         1156     1324     +168     
- Misses        150      156       +6     
Files with missing lines Coverage Δ
src/build-site.js 90.19% <100.00%> (+1.43%) ⬆️
src/database.js 95.23% <100.00%> (ø)
src/record.js 100.00% <100.00%> (ø)
src/gamedb-sync.js 95.89% <95.89%> (ø)

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fcd035a...7191c6f. Read the comment docs.

@sonarqubecloud

Copy link
Copy Markdown

@ReenigneArcher
ReenigneArcher merged commit 2fd6398 into master Sep 24, 2026
16 checks passed
@ReenigneArcher
ReenigneArcher deleted the feat/sync-gamedb-steam branch September 24, 2026 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants