1. You must have a GitHub service authorized to CumulusCI. If you're running locally/interactively, you do this by running cci service connect github. If you're running headlessly, you'll use environment variables.
2. As the message says, you must have pushed the commit you're working on so that there's a place to put the commit status.
3. You run the flow build_unlocked_test_package. If this succeeds, you should be able to see a commit status on your commit in GitHub, which will have an 04t package version id in the description.
4. Then, you can run qa_org_unlocked. Note that you must still have the commit from (3) checked out in your local working directory.

If you've done all four of these steps and it's still not working, please edit some additional detail into your questions and I can help triage.

(Edited because I myself forgot a step).

1. You must have a GitHub service authorized to CumulusCI. If you're running locally/interactively, you do this by running cci service connect github. If you're running headlessly, you'll use environment variables.

2. As the message says, you must have pushed the commit you're working on so that there's a place to put the commit status.

3. You run the flow build_unlocked_test_package. This flow should show you an 04t package version id in your logs. I would typically pipe this log to a file by doing

   cci flow run build_unlocked_test_package --org dev | tee cumulusci.log
   

4. Use a shell script to grab the package id out of the log and send it to GitHub. We typically implement this as part of build automation rather than in CumulusCI itself, for complicated historical reasons. Here's one implementation:

STATUS=$(cat cumulusci.log | grep -o '04t[a-zA-Z0-9]*')
gh api \
    --method POST \
    -H "Accept: application/vnd.github.v3+json" \
    '/repos/YOUR_REPO/statuses/COMMIT_SHA' \
    -f state='success' \
    -f description="version_id: $STATUS" \
    -f context='Build Unlocked Test Package'

You would need to ensure that the GITHUB_TOKEN environment var is set to a valid GitHub API token, and install the gh CLI, to use this strategy. You'd need to substitute YOUR_REPO and COMMIT_SHA, likely with other environment vars, based on how your build system exposes that data.

If this succeeds, you should be able to see a commit status on your commit in GitHub, which will have an 04t package version id in the description.

At that point, you can run qa_org_unlocked. Note that you must still have the commit from (3) checked out in your local working directory.

If you've done all of these steps and it's still not working, please edit some additional detail into your questions and I can help triage.