Digital signatures for RP2350 boards

Development
141

OK, this requires two features working together:

  1. CODEOWNERS
  2. Branch Protection

Remember to lock down not only the public certificate, but also lock down the /.github/CODEOWNERS file itself!

The only tricky bit is that the setting to require review from a code owner is hidden by default, and only shown after the Require a pull request before merging option is enabled:

image
image1191×867 56.8 KB

I recommend enabling at least the first three of those five checkboxes. for personal github repositories, only the owner can modify these settings … so I cannot do this on your behalf (Sorry!).

1 Like
142
Sample CODEOWNERS file

# Require Ian or Henry to review changes to...

# Changes to the public key, or cert commands
/src/pubkey/                   @DangerousPrototypes @henrygab
/src/commands/global/cert.*    @DangerousPrototypes @henrygab

# Modifications to CMakeLists.txt can change which files are included in the build
CMakeLists.txt                 @DangerousPrototypes @henrygab

# Anything in github directory (workflows, codeowners, etc.)
/.github/                      @DangerousPrototypes @henrygab
/.devcontainer/                @DangerousPrototypes @henrygab
/.vscode/                      @DangerousPrototypes @henrygab
/LICENSE.TXT                   @DangerousPrototypes @henrygab
/.gitignore                    @DangerousPrototypes @henrygab
/.gitmodules                   @DangerousPrototypes @henrygab
/docker-compose.yml            @DangerousPrototypes @henrygab

Then, add the branch protection rules as noted above…

1 Like
143

Thank you, I will get this set up.

1 Like
144

This should be setup now. I applied it to all branches.

1 Like