I can’t work out how to manually trigger the Checks process against the latest commit in a repo. Is this possible?
To replicate a scenario where you would need to do this, in a Python code repository submit a commit which will write a new tranforms-shrinkwrap.yml and also uses a new Spark profile that hasn’t been imported.
Checks will fail. The shrinkwrap file injects a commit without triggering a new Checks process.
I can go into the Code Repo settings and import the missing Spark profile, but I can’t re-trigger the Checks process because it is against an old commit hash. The only workaround I’ve found is to make a code change. Change a comment, add some whitespace, etc. and submit a new commit, but that feels like the wrong solution.
Hey your read here is correct. Checks are tied to commit hashes, so when HEAD moves past your failed Check, retrigger is disabled because the results wouldn’t reflect the current branch state.
Why the Retrigger button is disabled:
Checks bind to a specific commit hash. When transforms-shrinkwrap.yml auto-commits, HEAD advances. Your failed Check is now behind HEAD, so the platform won’t retrigger it as the results wouldn’t represent the current branch state.
To get unstuck (what you’re already doing):
Trivial commit — a whitespace change, comment edit, or empty commit to advance HEAD and trigger a fresh Check will work and is a standard workaround when you’re already here.
To avoid it next time:
Import the Spark profile before committing — Settings → Spark → Add profiles → import NUM_EXECUTORS_32 before you commit your code.
Alternative workflow:
Use a feature branch — fix the profile, push a trivial change, let Checks run clean on the branch before merging to master allowing you to keep the noise off your main branch if you’re doing this repeatedly.
Docs: Code Repositories — Checks and Spark profile configuration
