RES-0000: updated notebook to correctly grab the public key from the … #69
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Echoes HQ / Echoes - Labels check
required action
Jan 15, 2025 in 0s
Label validation failed
| Dimension | Required | Present | Check result |
|---|---|---|---|
| Effort Estimation of the effort invested in this change |
No | Default (XS) | ✅ |
| Impediment Impediments encountered while completing this change |
No | No | ✅ |
| Intent The intended outcome motivating the change |
No | No | ✅ |
| Type The type of change or issue |
Yes | No | ❌ Missing label for required dimension |
Why am I seeing this check?
Echoes lets engineeering teams categorize work consistently across teams and product development tools. The data is surfaced into dashboards that shine a light on your work and helps management understand the reality of the activity. Labels are centrally defined in Echoes to represent what matters to your organization. Echoes keep them in sync across all of your repositories so you don't have to.
- Pull requests linked to a GitHub issue automatically inherit its labels.
- Pull requests linked to a ticket in another system on which Echoes is enabled (e.g., referencing a JIRA ticket in the title) automatically inherit its labels.
- This check can be optionally disabled on a team-per-team basis (see the documentation).
Loading