Skip to content

Actions: yiisoft/db-migration

Actions

backwards compatibility

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
bc.yml
166 workflow runs
166 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Update package configuration from #360 backwards compatibility #285: Pull request #366 opened by vjik
29s improve-config
improve-config
29s
Introduce runtime directory (#365) backwards compatibility #284: Commit abb3d99 pushed by vjik
24s master
master
24s
Introduce runtime directory backwards compatibility #283: Pull request #365 opened by vjik
58s runtime-dir
runtime-dir
58s
Add migrate:mark command to manage migration history backwards compatibility #282: Pull request #364 synchronize by samdark
1m 17s issue-363-migrate-mark
issue-363-migrate-mark
1m 17s
Add migrate:mark command to manage migration history backwards compatibility #281: Pull request #364 synchronize by samdark
29s issue-363-migrate-mark
issue-363-migrate-mark
29s
Add migrate:mark command to manage migration history backwards compatibility #280: Pull request #364 synchronize by samdark
32s issue-363-migrate-mark
issue-363-migrate-mark
32s
Add migrate:mark command to manage migration history backwards compatibility #279: Pull request #364 synchronize by samdark
31s issue-363-migrate-mark
issue-363-migrate-mark
31s
Add migrate:mark command to manage migration history backwards compatibility #278: Pull request #364 synchronize by github-actions Bot
1m 20s issue-363-migrate-mark
issue-363-migrate-mark
1m 20s
Add migrate:mark command to manage migration history backwards compatibility #277: Pull request #364 opened by samdark
2m 29s issue-363-migrate-mark
issue-363-migrate-mark
2m 29s
Fix #360: Support named database migration sets with --db selection… backwards compatibility #276: Commit 3c06394 pushed by samdark
28s master
master
28s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #275: Pull request #361 synchronize by samdark
1m 2s feature/named-migration-databases
feature/named-migration-databases
1m 2s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #274: Pull request #361 synchronize by samdark
56s feature/named-migration-databases
feature/named-migration-databases
56s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #273: Pull request #361 synchronize by samdark
31s feature/named-migration-databases
feature/named-migration-databases
31s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #272: Pull request #361 synchronize by samdark
58s feature/named-migration-databases
feature/named-migration-databases
58s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #271: Pull request #361 synchronize by samdark
1m 48s feature/named-migration-databases
feature/named-migration-databases
1m 48s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #270: Pull request #361 synchronize by samdark
1m 2s feature/named-migration-databases
feature/named-migration-databases
1m 2s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #269: Pull request #361 synchronize by vjik
30s feature/named-migration-databases
feature/named-migration-databases
30s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #268: Pull request #361 synchronize by samdark
4m 31s feature/named-migration-databases
feature/named-migration-databases
4m 31s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #267: Pull request #361 synchronize by samdark
2m 0s feature/named-migration-databases
feature/named-migration-databases
2m 0s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #266: Pull request #361 synchronize by samdark
55s feature/named-migration-databases
feature/named-migration-databases
55s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #265: Pull request #361 synchronize by samdark
38s feature/named-migration-databases
feature/named-migration-databases
38s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #264: Pull request #361 synchronize by samdark
1m 24s feature/named-migration-databases
feature/named-migration-databases
1m 24s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #263: Pull request #361 synchronize by samdark
26s feature/named-migration-databases
feature/named-migration-databases
26s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #262: Pull request #361 synchronize by samdark
30s feature/named-migration-databases
feature/named-migration-databases
30s
Fix #360: Support named database migration sets with --db selection, a single configuration source for default, and separate migration history backwards compatibility #261: Pull request #361 synchronize by samdark
29s feature/named-migration-databases
feature/named-migration-databases
29s