Skip to content
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

Jump to bottom

add triage/confidential tag to docs #4678

Merged
merged 1 commit into from
Dec 11, 2023
Merged

add triage/confidential tag to docs #4678

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions docs/reference/airflow_tags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,5 @@ This tag is meant to provide guidance to a triage engineer on how to respond to
- **triage/record_only**: Failures should _only_ be recorded and the job owner informed without taking any active steps to fix the failure.

- **triage/no_triage**: No triage should be performed on this job. Should only be used in a limited number of cases, like this is still WIP, where no production processes are affected.

- **triage/confidential** - Failures should be recorded by the triage engineer as normal, and bug should be marked **Confidential**.