-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Use Global.Variables instead of JobContext and include action path/ref in the message. #2214
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.
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
Conversation
…f in the message.
88d96d5 to
4edba70
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't it be a bit better performance wise if we just appended the new warnings to the old ones? This way we just have to convert to json the new ones. :)
Sorry I was not able to edit the whole block so I just appended my suggestion at the bottom. 😃
20ae8c4 to
aa36449
Compare
aa36449 to
d839310
Compare
| { | ||
| if (!ExecutionContext.JobContext.ContainsKey("Node12ActionsWarnings")) | ||
| var repoAction = Action as RepositoryPathReference; | ||
| var warningActions = new HashSet<string>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using HashSet so we can remove duplication on the error message.
…f in the message. (actions#2214) * Use Global.Variables instead of JobContext and include action path/ref in the message. * encoding * .
We should not use
JobContextfor carrying runner internal data.