-
Notifications
You must be signed in to change notification settings - Fork 10.1k
actions: add number of action invocations to change summary #37400
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
The equivalence tests will be updated. Please verify the changes here. |
24a9969
to
6620dfc
Compare
The equivalence tests will be updated. Please verify the changes here. |
078fcbf
to
5f0f500
Compare
The equivalence tests will be updated. Please verify the changes here. |
The equivalence tests will be updated. Please verify the changes here. |
5f0f500
to
cba282c
Compare
The equivalence tests will be updated. Please verify the changes here. |
cba282c
to
baabcb1
Compare
The equivalence tests will be updated. Please verify the changes here. |
baabcb1
to
572e9c1
Compare
The equivalence tests will be updated. Please verify the changes here. |
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.
Overall LGTM, but what do you think about making the output more consistent? I prefer this:
Resources: 1 added, 0 changed, 0 destroyed.
Actions: 1 invoked.
over the current:
Resources: 1 added, 0 changed, 0 destroyed.
1 Action invoked.
Sounds like a good idea, I'll do that tomorrow 👍 |
The equivalence tests will be updated. Please verify the changes here. |
49f969b
to
360856a
Compare
The equivalence tests will be updated. Please verify the changes here. |
360856a
to
539f24e
Compare
The equivalence tests will be updated. Please verify the changes here. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Fixes #
Target Release
1.14.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry