Fix branch checks for content publication CI/CD.

[aj-stein-nist]

Committer Notes

This is a short-term fix to #117 until #116 lands as a more systemic fix.

A test merge and completed run of this minor CI/CD tweak in my main branch of my developer fork can be found in aj-stein-nist/oscal-content@bfe21e1. This is workflow run to validate this change will publish accordingly.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?

[aj-stein-nist]

@david-waltermire-nist this is good to go, I didn't understand why auto-publish was still skipped in this job run but it is because (as I learned debug mode) that I cannot set HOME_REPO in the PR and not invalidate the PR to show a valid test. It should now work though!

[david-waltermire]

Thanks!