Ankush Menat b140bb3f43 test: run patch test to last release and PR ... In the patch test, instead of migrating to the current SHA directly. Migrate to the latest release (with code at the time of release) and then migrate to last commit in PR. Why? When directly migrating, the previous patches that would've run with old code have access to the new code and it's not realistic. This change brings it a little bit closer to reality. Hence missing failures that would occur with IRL installations.		2021-09-21 18:14:17 +05:30
..
docker-release.yml	ci: Update names for GHA workflows and jobs	2020-11-04 12:27:14 +05:30
docs-checker.yml	fix: Drop support for Python 3.6	2021-09-17 11:24:51 +05:30
patch-mariadb-tests.yml	test: run patch test to last release and PR	2021-09-21 18:14:17 +05:30
publish-assets-develop.yml	fix: Drop support for Python 3.6	2021-09-17 11:24:51 +05:30
publish-assets-releases.yml	fix: Drop support for Python 3.6	2021-09-17 11:24:51 +05:30
semgrep.yml	ci: make semgrep check diff-aware	2021-07-16 12:00:30 +05:30
server-mariadb-tests.yml	Merge branch 'develop' into ci_ubuntu_latest	2021-09-07 13:10:56 +05:30
server-postgres-tests.yml	Merge branch 'develop' into ci_ubuntu_latest	2021-09-07 13:10:56 +05:30
ui-tests.yml	ci: use ubuntu-latest for all jobs	2021-08-31 22:31:50 +05:30