Azeem Shaikh

> yes, that's the 143 issue above. I'll update the description. Thanks Ah sorry, didn't see it. My bad.

@justaugustus are you still planning to work on this? Would be good to announce this tool along with our v2 launch (aiming for a launch timeline of first week of...

Awesome thanks! Looking forward to it :)

@laurentsimon @naveensrinivasan fyi good testcase to add to our e2e tests - workflows which have `pull_request` (or other non-supported events enabled).

@ossf/scorecard-maintainers - thanks for all the awesome work on v2, we are (almost) ready for launch :) Aiming for a release in September 1st week. Some final pending items and...

@justaugustus ah you are right - https://semver.org/#spec-item-11. My bad. @naveensrinivasan - not sure yet. Still exploring my options through Cloud Endpoints.

The Dockerfile changes should be pushed to `golang-staging` branch. That'll automatically test this change for Golang action against the current bash action. Apart from that LGTM.

@laurentsimon you had mentioned you have a script for re-using existing issues? Could you point me to that?

Some more e2e tests needed given recent bugs: - [x] Create a single issue per workflow instead per-matrix value to reduce noise. - [ ] Add tests for a repository...

@spencerschrock when you add e2e for https://github.com/ossf/scorecard-action/issues/856 this issue can be resolved too. 2 things I'm not implementing and skipping: (i) Re-use existing issue instead of creating new one and...