You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The publish-charm workflow only ever checks the main branch for the branch protection rules, and ignores release branches. The workflow should at least accept an alternate branch or use the branch based on the workflow event which is triggering this job:
branch-up-to-date-check-enabled:
runs-on: ubuntu-22.04steps:
- uses: octokit/[email protected]id: get-branch-protectionenv:
GITHUB_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}with:
route: GET /repos/{owner}/{repo}/branches/{branch}/protection/required_status_checksrepo: ${{ github.event.repository.name }}owner: ${{ github.event.repository.owner.login }}branch: main # <---------- fixed to the main branch
- run: | if [ ${{ fromJson(steps.get-branch-protection.outputs.data).strict }} != "true" ]; then echo "::error::Strict checks are not enabled for this repository" exit 1 fi
The text was updated successfully, but these errors were encountered:
The publish-charm workflow only ever checks the
main
branch for the branch protection rules, and ignores release branches. The workflow should at least accept an alternate branch or use the branch based on the workflow event which is triggering this job:The text was updated successfully, but these errors were encountered: