Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optional extra checks of "modified" schema after pull/push

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
postgresql, python
Domain
databases

Research direction

No file or test is named. Start by locating the pull and push entry points and the existing schema-comparison logic; then determine where an opt-in check can run after each operation. Done means the option verifies both requested comparisons and reports any changes.

Written by the indexing model from the issue text.

Description

enhancement

For troubleshooting, it may be useful to have an option that would do an extra sanity check after each pull/push - it would verify that:

  • comparing geopackage at the latest version and the "modified" schema gives no changes
  • comparing "modified" schema and "base" schema gives no changes
Dominant language
Python
Stars
53
Forks
25
Avg merge
1m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.