Angela P Wen

I'm correctly hitting the case where the database isn't finalized now, and just need to implement the zipping of the partial database files. I see [documentation for the CLI command](https://codeql.github.com/docs/codeql-cli/manual/database-bundle/)...

I think perhaps splitting the PR check file into 2 jobs, one for running everything before checking artifact downloads, and one for just checking artifact downloads with a `needs` dependency...

I've made most of the requested changes, and will work on the refactoring for unit tests. I also made the change to zip up the database bundle and it seems...

I added `//TODO`s in locations where I am planning to unit test, with the description of what each unit test should do, to get feedback on the planned tests before/while...

Quickly closing and re-opening to trigger new PR checks from actions/toolkit#1160

I am working on integration testing with a new PR check (Debug artifact upload after failure) and have a few thoughts: - with the `init` step, I was previously only...

> Let's not worry about this for now. We could try to convince `init` to fail by giving it malformed input arguments or config file, but I think `init` itself...

What future PR checks will see. Hopefully this gets the message across? Maybe `Failure Intended` would be even more clear 😄

The remaining unit tests are up, requesting final review now 😄 After this is merged, I will add the "Download and check debug artifacts after failure in analyze" PR check/job...

Started at https://github.com/github/vscode-codeql/pull/1457