You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
make sure backup csv doesn't run automatically (#249)
# Summary
### Build variant adjustments:
* Removed the `backup_csv_images` build variant from the general
`buildvariants` section, including its tasks and tags.
* Re-added the `backup_csv_images` build variant under the `manual patch
only` section, specifying `allowed_requesters` as `"patch"` and
retaining the same tasks and `run_on` configuration.
-> this makes sure it only runs if manually triggered
## Proof of Work
- after master merge this shouldn't show in waterfall
## Checklist
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [ ] Have you checked whether your jira ticket required DOCSP changes?
- [ ] Have you checked for release_note changes?
## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
* **blocking**: Must be addressed before approval.
* **follow-up**: Can be addressed in a later PR or ticket.
* **q**: Clarifying question.
* **nit**: Non-blocking suggestions.
* **note**: Side-note, non-actionable. Example: Praise
* --> no prefix is considered a question
0 commit comments