-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
database: Add versions.yank_message
column
#9274
database: Add versions.yank_message
column
#9274
Conversation
1dd5c45
to
c9d832b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔢 Self-check (PR reviewed by myself and ready for feedback.)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9274 +/- ##
==========================================
- Coverage 89.29% 89.14% -0.15%
==========================================
Files 282 283 +1
Lines 28629 28823 +194
==========================================
+ Hits 25563 25693 +130
- Misses 3066 3130 +64 ☔ View full report in Codecov by Sentry. |
versions.yank_message
column
Signed-off-by: hi-rustin <[email protected]>
d7d3eab
to
7083232
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔢 Self-check (PR reviewed by myself and ready for feedback.)
ref #9193
In this PR, I added a new column to the
versions
table.I picked the text here. For a simple text-based message, I think the length is enough.
I am not sure if we should consider using JSONB here to accommodate the possibility of needing to store more structured information in the future.
I also marked it private, I guess before we expose the new API to users, we should keep it private.