Skip to content

Disable automatic sync schedule in sync-db.yml#693

Merged
rdimitrov merged 1 commit intomainfrom
temp-disable-db-sync-job
Oct 22, 2025
Merged

Disable automatic sync schedule in sync-db.yml#693
rdimitrov merged 1 commit intomainfrom
temp-disable-db-sync-job

Conversation

@rdimitrov
Copy link
Member

Motivation and Context

We have some more work to do on that so let's temporarily comment out the scheduled cron job for syncing the database.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Temporarily comment out the scheduled cron job for syncing the database.
@rdimitrov rdimitrov requested a review from domdomegg October 22, 2025 09:34
@rdimitrov rdimitrov enabled auto-merge (squash) October 22, 2025 13:57
@rdimitrov rdimitrov merged commit d704192 into main Oct 22, 2025
5 checks passed
@rdimitrov rdimitrov deleted the temp-disable-db-sync-job branch October 22, 2025 20:16
slimslenderslacks pushed a commit to slimslenderslacks/registry that referenced this pull request Dec 18, 2025
)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
We have some more work to do on that so let's temporarily comment out
the scheduled cron job for syncing the database.

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->
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