Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: aggregate test results for required statuses #592

Merged
merged 2 commits into from Jul 12, 2022

Conversation

ericswanson-dfinity
Copy link
Member

@ericswanson-dfinity ericswanson-dfinity commented Jul 12, 2022

Description

Status check names include matrix elements. This means that required status names would have to change if any of those matrix elements changed in the future.

This change aggregates these checks into a single status check with a constant name, suitable for use as a required status.

These are the new statuses:
Screen Shot 2022-07-12 at 1 49 51 PM

Fixes https://dfinity.atlassian.net/browse/SDK-582

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

  • My changes follow the guidelines in CONTRIBUTING.md.
  • The title of this PR complies with Conventional Commits.
  • (no need) I have edited the CHANGELOG accordingly.
  • (no need) I have made corresponding changes to the documentation.

Status check names include matrix elements.  This means that required status names would have to change if any of those matrix elements changed in the future.

This change aggregates these checks into a single status check with a constant name, suitable for use as a required status.

Fixes https://dfinity.atlassian.net/browse/SDK-582
@ericswanson-dfinity ericswanson-dfinity requested a review from a team as a code owner July 12, 2022 20:45
@krpeacock krpeacock merged commit 968530c into main Jul 12, 2022
@krpeacock krpeacock deleted the ericswanson/sdk-582-required-statuses branch July 12, 2022 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants