Separate the concerns: dependabot and manual PR labelling for testing

[zinduolis]

Category

Core Functionality

Feature/Issue Description

Q: Please give a brief summary of your feature/fix
A: Fixes dependabot auto-merge by running BrowserStack tests automatically for dependabot PRs, without bypassing branch protection for other PRs.

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

• Split into two workflows to avoid GitHub's "skipped job = passed check" branch protection bypass
• github_actions.yml: reverted to labeled-only trigger, added concurrency group, added try/catch on label removal
• dependabot_auto_label.yml (new): on opened/synchronize, auto-applies safe_to_test label for dependabot[bot] PRs only, which triggers the BrowserStack workflow via the labeled event

Test Cases

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

• Dependabot PRs: auto-labeled → BrowserStack runs → auto-merge proceeds
• Fork PRs: no auto-label → required check stays pending → merge blocked until maintainer labels
• Non-fork PRs: same as fork — no BrowserStack check created without label → merge blocked
• Dependabot push updates: remove+re-add label ensures a fresh labeled event fires each time
• Concurrent runs: concurrency with cancel-in-progress prevents duplicate BrowserStack runs

Wiki Page

N/A