- [ ] Have you followed the guidelines for contributing? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] Have you successfully run `make lint && make test`? - [ ] Have you added an entry to the changelog (`docs/reference/changelog.rst`)? --- ## Description Tests craft-application qa.yaml workflow against starflow PR #101 changes before merging in both repositories. ## Changes - Updated `.github/workflows/qa.yaml` to reference `@copilot/use-pristine-ubuntu-action` (the actual branch name from starflow PR #101) instead of `@main` for starflow workflows - Added header comments linking to https://github.com/canonical/starflow/pull/101 All 2 workflow references now point to the PR branch: - `canonical/starflow/.github/workflows/lint-python.yaml@copilot/use-pristine-ubuntu-action` - `canonical/starflow/.github/workflows/test-python.yaml@copilot/use-pristine-ubuntu-action` **Note**: This is temporary for cross-repo validation. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > Create a test pull request that evaluates changes to the GitHub Actions workflow qa.yaml, similar to the approach used in canonical/craft-parts#1412. This should include updates or additions that facilitate testing of the workflow or related process, referencing the changes or process established in PR #101 of the starflow project, if applicable. The intent is to validate that the qa.yaml workflow functions properly with those types of updates, similar to what was done in craft-parts. </details> <!-- START COPILOT CODING AGENT SUFFIX --> *This pull request was created as a result of the following prompt from Copilot chat.* > Create a test pull request that evaluates changes to the GitHub Actions workflow qa.yaml, similar to the approach used in canonical/craft-parts#1412. This should include updates or additions that facilitate testing of the workflow or related process, referencing the changes or process established in PR #101 of the starflow project, if applicable. The intent is to validate that the qa.yaml workflow functions properly with those types of updates, similar to what was done in craft-parts. <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/canonical/craft-application/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.