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

Consider using RESULT / JOB_RESULT instead of parsing message #6

Open
benjumanji opened this issue Jun 17, 2018 · 0 comments
Open

Consider using RESULT / JOB_RESULT instead of parsing message #6

benjumanji opened this issue Jun 17, 2018 · 0 comments

Comments

@benjumanji
Copy link

I imagine this change (broadens) the scope of what emails get sent, so you might not like it as a breaking change. I am probably going to this anyway with a fork for me, but if you'd like the change pulled in I'll contribute once I have tested it. If not feel free to close.
@benjumanji benjumanji changed the title Consider using RESULT and / or JOB_RESULT instead of parsing message Consider using RESULT / JOB_RESULT instead of parsing message Jun 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@benjumanji