📖 Add correct contact to CODE_OF_CONDUCT.md

[calebbrown]

Signed-off-by: Caleb Brown [email protected]

What kind of change does this PR introduce?

Docs Update

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

[INSERT CONTACT METHOD] is in the code of conduct.

What is the new behavior (if this is a feature change)?**

Replace [INSERT CONTACT METHOD] with actual contact [email protected] (as verified in Slack).

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

NONE

Special notes for your reviewer

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

NONE

[codecov]

Codecov Report

Merging #2508 (576a0a2) into main (47be523) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2508   +/-   ##
=======================================
  Coverage   40.40%   40.40%           
=======================================
  Files         122      122           
  Lines        9908     9908           
=======================================
  Hits         4003     4003           
  Misses       5624     5624           
  Partials      281      281           

[github-actions]

Integration tests success for
[f36bf9a]
(https://github.com/ossf/scorecard/actions/runs/3598695198)

[github-actions]

Stale pull request message

[github-actions]

Integration tests success for
[98682e2]
(https://github.com/ossf/scorecard/actions/runs/3681577983)

[olivekl]

Sorry for the delay. Thanks for this, LGTM & approval.

[github-actions]

Integration tests success for
[bd7f06f]
(https://github.com/ossf/scorecard/actions/runs/3697570359)

[github-actions]

Integration tests success for
[3e872d1]
(https://github.com/ossf/scorecard/actions/runs/3746160476)

[spencerschrock]

The CI will never succeed for this, we'll need to fix the workflow:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

[spencerschrock]

There doesn't seem to be any native way of fixing the skipped checks, for reasons that this blog sums up well.
https://blog.pantsbuild.org/skipping-github-actions-jobs-without-breaking-branch-protection/

[laurentsimon]

There doesn't seem to be any native way of fixing the skipped checks, for reasons that this blog sums up well. https://blog.pantsbuild.org/skipping-github-actions-jobs-without-breaking-branch-protection/

I've not read the link, but I think you can declare an additional job that depends on the skipped, and mark the new job if: always() and use that job in branch protection. We do something similar on the SLSA repos.

[spencerschrock]

There doesn't seem to be any native way of fixing the skipped checks, for reasons that this blog sums up well. https://blog.pantsbuild.org/skipping-github-actions-jobs-without-breaking-branch-protection/

I've not read the link, but I think you can declare an additional job that depends on the skipped, and mark the new job if: always() and use that job in branch protection. We do something similar on the SLSA repos.

I think this is a little different. The jobs are never scheduled due to the path filtering at the top. I don't think always() would run as the job isn't skipped, it's never scheduled. But I can try an experiment.

[github-actions]

Stale pull request message

[github-actions]

Integration tests success for
[81345a3]
(https://github.com/ossf/scorecard/actions/runs/3878816529)

[github-actions]

Integration tests success for
[576a0a2]
(https://github.com/ossf/scorecard/actions/runs/3907189479)