Is your feature request related to a problem? Please describe.
When using reg-suit with a mono-repo containing multiple, standalone frontend applications,
where each application has it's own reg-suit job running, only the vrt that finished last is shown/linked in the comment and in the status section.
Describe the solution you'd like
Ideally, you would be able to specify an optional namespace or scope parameter on the github extension settings,
which would then be used both when updating the comment (not updating other namespace's comments), as well as when reporting statuses (one status maintained for each namespace).
Describe alternatives you've considered
I considered just doing the reporting bit (at least the status reporting) myself using the gh cli tool, but then I would have to parse out the actual results from the reg-suit output, and re-implement a lot of other stuff.
At least for the comment, you can actually see previous reports by using the edit history, so that is at least a workaround.
Additional context
Will provide if necessary!
Is your feature request related to a problem? Please describe.
When using
reg-suitwith a mono-repo containing multiple, standalone frontend applications,where each application has it's own
reg-suitjob running, only the vrt that finished last is shown/linked in the comment and in the status section.Describe the solution you'd like
Ideally, you would be able to specify an optional
namespaceorscopeparameter on the github extension settings,which would then be used both when updating the comment (not updating other
namespace's comments), as well as when reporting statuses (one status maintained for each namespace).Describe alternatives you've considered
I considered just doing the reporting bit (at least the status reporting) myself using the
ghcli tool, but then I would have to parse out the actual results from thereg-suitoutput, and re-implement a lot of other stuff.At least for the comment, you can actually see previous reports by using the edit history, so that is at least a workaround.
Additional context
Will provide if necessary!