Echoes lets you express the motivation behind pull requests simply through GitHub labels. We surface this data into dashboards that shine a light on your work and help understand the reality of the activity.

We don't surface any individualized data, nor performance metrics, nor scores. The goal is to help organizations set clearer goals, improve focus, and offer a better context overall for engineers to deliver their best work. This starts by giving managers an accurate understanding of the reality of the teams.

How to use

TL;DR: use the labels prefixed with echoes/ to tag your pull requests. That's all! No need for additional tickets, time-tracking, or switching to a different tool.

These labels are centrally defined in Echoes to represent what matters to your organization, and we keep them in sync across all of your repositories so you don't have to.

Echoes requires pull requests to be tagged with at least one intent or initiative, and optionally with the effort that went into it.

Read more about Echoes fundamentals on this documentation page!

FAQ

Q: What if I don't know which label to set for a particular pull request?
Leave it blank! It's better to have some untagged items rather than randomly tagged pull requests.

Q: Can I add a new echoes/ label from GitHub if needed?
No: Echoes will regularly reconcile labels on repositories with its configuration and your label will get deleted. New labels must be added from Echoes configuration and will then get published on all repositories.

Q: Will it make any difference on results if I send fewer/more, or smaller/larger pull requests?
No: Echoes doesn't look at the diff, nor at the absolute number of pull requests. You can continue contributing exactly as you're used to, with the minor change of adding labels!

Q: Can we disable the automated GitHub check on pull requests?
Yes: you can disable the check on a team-per-team basis within Echoes configuration.