Repository navigation
Add compound index for repetition release lookups - #686
Merged
Merged
Conversation
neSpecc
approved these changes
Oct 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add a { groupHash: 1, release: 1 } index to repetition collections created for new projects.
Add a migration to create the index on existing repetitions:* collections in the events database.
Update the project creation test to verify the new index.
The migration uses MONGO_EVENTS_DB_URL to connect to the events database.
The release validator uses this index to find which releases each event appeared in, so it can determine when an event is resolved. codex-team/hawk.workers#590