Skip to content
Update database

Store custom sources in SQL instead of blobs #1229

Sign in to view logs

Store custom sources in SQL instead of blobs

Store custom sources in SQL instead of blobs #1229

Triggered via issue August 1, 2024 12:09
@andchiindandchiind
commented on #1693 eeb8531
Status Success
Total duration 2m 9s
Artifacts –

updateDatabase.yml

on: issue_comment
base_check
5s
base_check
get_review_state
4s
get_review_state
database_update_start
6s
database_update_start
if_not_approved_then_stop
0s
if_not_approved_then_stop
run_migrations  /  run_migrations
55s
run_migrations / run_migrations
database_success
6s
database_success
database_failure
0s
database_failure
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
base_check
Unexpected input(s) 'content', valid inputs are ['route', 'mediaType']
database_update_start
The following actions uses Node.js version which is deprecated and will be forced to run on node20: peter-evans/create-or-update-comment@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
database_success
The following actions uses Node.js version which is deprecated and will be forced to run on node20: peter-evans/create-or-update-comment@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/