ci(root): attempt fix for commits not associated to branch

[cloudratha]

📲 What

Commits raised in CI do not belong to any branches.
Not quite sure why, but believe it to be a combination of not specifying the ref in checkout and branch protection.
Explicitly calling the ref, I hope to see tags associated to commits that belong to a branch.

🤔 Why

When we do a release we gather tags from commits. It will not observe commits that do not belong to any branches, resulting in the incorrect semver version produced which causes catastrophic failure when trying to push the same version up to npm.

✅ Acceptance criteria Checklist

• Code peer reviewed?
• Documentation has been updated to reflect the changes?
• Passing all automated tests, including a successful deployment?
• Passing any exploratory testing?
• Rebased/merged with latest changes from development and re-tested?
• Meeting the Coding Standards?

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit d82c749. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx affected --base=last-release --target=e2e --parallel=1

---

Sent with 💌 from NxCloud.