Coordinate multi-repo issues better

[mulkieran]

Sometimes we have to manually coordinate PRs in several repos to address one new feature.

We would like to set up GitHub Workflows so that this can be handled automatically if we can agree on a standard naming scheme for the issues.

New features usually break stratisd CI on the stratis-cli tests and the testing tests. It would be nice if the CI would automatically look for the correct repo and the correctly named branch or PR and just use that to run the test.

[mulkieran]

Our current challenge example is issue-stratisd-3805. What should be the name of the passing stratis-cli PR? Actually giving it the exact same name could be reasonable.

[mulkieran]

The biggest technical difficulty is mapping from a name to a ref spec that can be used to specify the PR. I don't believe there is an available GitHub Action to do that. So, we would have to do that calculation ourselves. And now, we're into writing our own GitHub Action territory. The difficulty is that, through git actions we can actually obtain the prs, by number. But we need to use the GitHub API or gh to get the name of the PR from the number in order to determine what number we want to use as a ref.

[mulkieran]

I filed an issue with the checkout action upstream as I believe that I have found a bug: actions/checkout#2140 .

Assuming I'm correct, once that bug is fixed it will be easy to specify the interesting PR via simply changing the ref spec to the one from the appropriate PR.

We will still have not solved the name to PR id mapping problem, but we will be closer.

[mulkieran]

I figured out the refspec that would work as noted in actions/checkout#2140 . So, now we just need to persuade checkout to handle the PR id mapping problem.