Skip to content

Implement safe_to_test label and update outdated github actions#3521

Merged
zinduolis merged 1 commit intomasterfrom
red/safe_to_test_label
Mar 2, 2026
Merged

Implement safe_to_test label and update outdated github actions#3521
zinduolis merged 1 commit intomasterfrom
red/safe_to_test_label

Conversation

@zinduolis
Copy link
Copy Markdown
Contributor

@zinduolis zinduolis commented Mar 2, 2026

Pull Request

Category

Core Functionality

Feature/Issue Description

Q: Please give a brief summary of your feature/fix
A: Hardens BrowserStack CI by requiring a safe_to_test label before running tests on PRs from forks. Upgrades outdated actions.

Q: Give a technical rundown of what you have changed (if applicable)
A:

  • Workflow triggers only on labeled event, gated by safe_to_test label
  • Label is auto-removed as the first step, requiring re-approval for subsequent runs
  • Upgraded actions/checkout v4 → v6,
  • Added actions/github-script v8,
  • Maintainers must add the safe_to_test label after reviewing PR code. The label is consumed on use and must be re-added for each test run. Create the label in Settings → Labels.

Test Cases

Q: Describe your test cases, what you have covered and if there are any use cases that still need addressing.
A:

  • Workflow does not trigger without the label
  • Label is removed before secrets are accessed
  • New commits require label to be re-added

Wiki Page

N/A

@zinduolis zinduolis deployed to Integrate Pull Request March 2, 2026 05:43 — with GitHub Actions Active
@zinduolis zinduolis merged commit 997a2e0 into master Mar 2, 2026
5 checks passed
@zinduolis zinduolis deleted the red/safe_to_test_label branch March 2, 2026 06:03
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.

1 participant