Repository navigation
feat(custom links): SQL migration - #8017
logiczsniper wants to merge 1 commit into
Conversation
Pull request changelogAppAddedChangedDeprecatedRemovedFixedSecurityWebsiteAddedChangedDeprecatedRemovedFixedSecurityHostingAddedChangedDeprecatedRemovedFixedSecurity |
|
Maintainers - in the docs, I didn't see any information on your process for the SQL migrations - I would appreciate any guidance yous could give here 🙇 |
|
this is a feature we're working on ourselves, so we won't be accepting a third party contributions for this |
|
@Prospector okay cool, thanks! Is there some way that I can tell myself what is being worked on / what not? Is there some line drawn dividing work that you will accept open source contributions from? |
|
Generally, we only accept third party PRs for small bug fixes that also only need a small diff to fix. Anything larger or that requires design work is unlikely to get merged |
|
@Prospector OK cool, so is there any way to get more involved in that design work? I.e. if I offered you a design for how it would look first. For example for this issue of allowing custom links, the design is pretty straightforward so it felt like I could take a stab at it (but I understand in this case, one of yous is already working on, so this is an exception). |
Step 1 as listed in my plan towards #7807.
I opted for a single
jsonbcolumn here because:Added a default value here for backwards compat.