Update DB reminder readme #3765
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
Updates the database reminder message in the nitpicks configuration to reflect that 2 autopilot instances run in parallel during deployment, requiring careful handling of DB-breaking changes.
- Reformatted existing reminders as bullet points for better readability
- Added guidance for handling breaking changes with parallel autopilot instances
- Provided a workaround strategy for safe deployment of DB-breaking changes
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
m-sz
reviewed
Oct 10, 2025
m-sz
approved these changes
Oct 10, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the DB reminder message, since currently 2 auctions are running in parallel on each deployment, and this should be taken into account when committing DB-breaking changes.