Compliant Updates

[nyarly]

Description

Optionally allow commits and PRs to be made using a token.
Documents how to use this to get verified commits and PRs that trigger further actions.

Checklist

• Tested functionality against a test repository (see "How to test changes")
• Added or updated relevant documentation (leave unchecked if not applicable)

[nyarly]

@cole-h updated based on CI

[cole-h]

Hey there, sorry it took me so long to get back to you! I was doing a bit of playing around with your approach, and I was able to find a slightly better approach.

[cole-h]

Rather than dealing with the "get a verified-by-github commit" ourselves, I would much rather call out to an action or two that do this for us. And it just so happens that there is a combination of actions we can use to get the same result:

      - name: Create branch for ${{ inputs.branch }}
        if: ${{ inputs.commit-with-token == 'true' }}
        uses: peterjgrainger/action-create-branch@v2.2.0
        env:
          GITHUB_TOKEN: ${{ inputs.token }}
        with:
          branch: refs/heads/${{ inputs.branch }}
      - name: Create GitHub-verified commit
        if: ${{ inputs.commit-with-token == 'true' }}
        uses: swinton/commit@v2.0.0
        env:
          GH_TOKEN: ${{ inputs.token }}
        with:
          files: |
            flake.lock
          commit-message: ${{ inputs.commit-msg }}
          ref: refs/heads/${{ inputs.branch }}

You can see it works here: cole-h/test#7.

[nyarly]

Let me try this on my fork