# Checklist
- [x] I have read the [contribution guidelines] (https://github.com/Azure/azure-iot-sdk-c/blob/main/.github/CONTRIBUTING.md).
- [ ] I added or modified the existing tests to cover the change (we do not allow our test coverage to go down).
- If this is a modification that impacts the behavior of a public API
- [ ] I edited the corresponding document in the `devdoc` folder and added or modified requirements.
- I submitted this PR against the correct branch:
- [x] This pull-request is submitted against the `main` branch.
- [x] I have merged the latest `main` branch prior to submission and re-merged as needed after I took any feedback.
- [x] I have squashed my changes into one with a clear description of the change.
# Reference/Link to the issue solved with this PR (if any)
# Description of the problem
The ARM and the MIPS32 cross-compilation jobs in .vsts-ci.yml will always target the main branch, ignoring the branch a given PR is based on and letting potential issues sip through.
Description of the solution
This change fixes the ARM and MIPS32 jobs so they run against whatever branch the pipeline is running against.
The ARM and the MIPS32 cross-compilation jobs in .vsts-ci.yml will always target the main branch, ignoring the branch a given PR is based on and letting potential issues sip through.
Description of the solution
This change fixes the ARM and MIPS32 jobs so they run against whatever branch the pipeline is running against.