🌱 Limit integration tests to ones that work with the GITHUB_TOKEN. #2672
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Integration test change
What is the current behavior?
Some of the integration tests need access to GitHub secrets, specifically the branch protection e2e tests.
What is the new behavior (if this is a feature change)?**
The integration test trigger was changed to
pull_request
which does not have access to GitHub secrets.The status message when integration tests finish was removed to reduce the permissions of the GITHUB_TOKEN
Which issue(s) this PR fixes
Special notes for your reviewer
This was tested in another repo to verify the GITHUB_TOKEN was sufficient.
https://github.com/spencerschrock/scorecard-test/actions/runs/4188418627/jobs/7259527613
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.)