Organization-wide Workflow Add Instructions

[naveensrinivasan]

I picked up the PR #151

[codecov]

Codecov Report

Merging #773 (3973e3c) into main (7290c22) will decrease coverage by 11.16%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #773       +/-   ##
===========================================
- Coverage   74.80%   63.63%   -11.17%     
===========================================
  Files           2        4        +2     
  Lines         127      231      +104     
===========================================
+ Hits           95      147       +52     
- Misses         25       72       +47     
- Partials        7       12        +5     

Impacted Files	Coverage Δ
options/env.go	100.00% <0.00%> (ø)
signing/signing.go	32.14% <0.00%> (ø)
multi-repo-action/main.go	0.00% <0.00%> (ø)
options/options.go	84.28% <0.00%> (+9.88%)	⬆️

[naveensrinivasan]

@azeemshaikh38 @justaugustus @laurentsimon I need a 👍 to merge this in.

[laurentsimon]

Is the multi-repo tool ready?
Last time I checked, it would need a bit of logic to detect whether a previous PR was sent or not, in order to avoid duplication of issues.

[naveensrinivasan]

Is the multi-repo tool ready?
Last time I checked, it would need a bit of logic to detect whether a previous PR was sent or not, in order to avoid duplication of issues.

TBH I don't know. We can close this PR if it isn't ready. I picked up the long-running PR to close things.

[laurentsimon]

Is the multi-repo tool ready?
Last time I checked, it would need a bit of logic to detect whether a previous PR was sent or not, in order to avoid duplication of issues.

TBH I don't know. We can close this PR if it isn't ready. I picked up the long-running PR to close things.

I think it'd be good to iron out some of the problems. I'm just hesitant to release this if people start finding problems. I think the main feature that would be useful it avoid spamming if a person provides a repository where an issue is already opened. That'd a cool PR to work on though.

Wdut?

[justaugustus]

@naveensrinivasan -- In lieu of updating the instructions, I would actually remove any mentions on the tool (, but not the tool itself).

I merged some initial fixes to multi-repo-action in #301, but it is still not in a working state and I think leaving instructions in about it may cause more overhead than we need.

[naveensrinivasan]

@naveensrinivasan -- In lieu of updating the instructions, I would actually remove any mentions on the tool (, but not the tool itself).

I merged some initial fixes to multi-repo-action in #301, but it is still not in a working state and I think leaving instructions in about it may cause more overhead than we need.

I agree. There isn't any mention of the tool other than in its own folder and README. I will update the README with Work In Progress.

[naveensrinivasan]

closing this for #776