This pull request includes changes to the .github/workflows/evaluate.yaml file to improve the workflow for checking out pull requests and the default branch.
Workflow improvements:
.github/workflows/evaluate.yaml: Changed the job name from "Checkout pull request" to "Checkout default branch" and updated the action to actions/checkout@v4.
.github/workflows/evaluate.yaml: Updated the step to check out the actual pull request using gh pr checkout instead of hub pr checkout.
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
[ ] Yes
[X] No
Type of change
[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:
Purpose
This pull request includes changes to the
.github/workflows/evaluate.yaml
file to improve the workflow for checking out pull requests and the default branch.Workflow improvements:
.github/workflows/evaluate.yaml
: Changed the job name from "Checkout pull request" to "Checkout default branch" and updated the action toactions/checkout@v4
..github/workflows/evaluate.yaml
: Updated the step to check out the actual pull request usinggh pr checkout
instead ofhub pr checkout
.Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error? If you're not sure, try it out on an old environment.
Type of change
Code quality checklist
See CONTRIBUTING.md for more details.
python -m pytest
).python -m pytest --cov
to verify 100% coverage of added linespython -m mypy
to check for type errorsruff
manually on my code.