Use process labels#330
Merged
Merged
Conversation
josevalim
reviewed
Sep 9, 2025
josevalim
reviewed
Sep 9, 2025
Co-authored-by: José Valim <jose.valim@gmail.com>
Co-authored-by: José Valim <jose.valim@gmail.com>
josevalim
reviewed
Sep 9, 2025
Member
|
Thank you for the pull request. I believe this is a great addition. I have added some comments, so we also look up the name. |
Co-authored-by: José Valim <jose.valim@gmail.com>
Contributor
Author
|
@josevalim Awesome, thank you for the improvements! |
This comment was marked as resolved.
This comment was marked as resolved.
josevalim
reviewed
Sep 9, 2025
josevalim
reviewed
Sep 9, 2025
Member
|
💚 💙 💜 💛 ❤️ |
Member
|
Btw @nathanl , would you like to send a PR to Elixir that automatically adds |
Contributor
Author
|
@josevalim very much yes, I was going to try that next 😄 ❤️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This probably needs tweaking, but I periodically see people asking (and have wondered myself) how to figure out which test in a suite is responsible for something like
This is an attempt to make our systems and their errors easier to understand.