Skip to content

fix: pull request trigger name does not match the one configured in github branch protections #1045

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.

Sign up for GitHub

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

Merged
becksebenius-unity merged 2 commits into from
Aug 11, 2021
Merged

fix: pull request trigger name does not match the one configured in github branch protections #1045

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b40415
fix: pull request trigger name does not match the one configured in g…
becksebenius-unity Aug 11, 2021
47e0755
Moved the old name to a "legacy" job so that the branch protected can…
becksebenius-unity Aug 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .yamato/_triggers.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,12 @@ develop_nightly_trigger:
- .yamato/code-coverage.yml#code_coverage_win_{{ project.name }}
{% endfor -%}

# Legacy job that matches the name with branch protections as of 8/11
# Can be removed once branch protections are updated to the new name
pull_request_trigger_legacy:
name: Pull Request Trigger on 2021.1 (master, develop, & release branches)
dependencies:
- .yamato/_triggers.yml#pull_request_trigger

# Run all relevant tasks when a pull request targeting the develop
# branch is created or updated. Currently only mlapi package tests are
Expand Down