feat(github): update nix hash on relevant PR instead of main branch

[drewr]

Hopefully this addresses the root cause of #83 which is that staying on top of the generated PRs was challenging.

[scotwells]

@drewr have you confirmed this works? Think you should be able to modify the go.mod file to get this to execute.

[drewr]

I didn't think I could until the workflow was in main. Lemme try.

[drewr]

Looks like I can. 🤞

[drewr]

Well it doesn't not work...

Run arduino/setup-task@v2
Error: API rate limit exceeded for 68.220.59.211. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

[scotwells]

Looks like you don't need to emit status checks directly. Just need to make sure the pipeline fails when an error happens and have the pipeline end successfully if everything was updated or no updates were needed.

[drewr]

Not sure why it showed up both as its own check and under ctl testing, but those are separate. The only way to have that commit gate the PR being merged is for it to be a check.

[drewr]

OK, I think this works better. However, since there hasn't been a real deps change the hash hasn't needed updating, so there isn't a commit, but I can't see why that wouldn't have worked (famous last words).

[scotwells]

@drewr yeah a workflow by definition is a check. We'll just need to configure the branch protection policy to require that check complete before allowing the PR to be merged.