-
Notifications
You must be signed in to change notification settings - Fork 43
Changing actor name updates mappings and credentials store #285
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
…kup and platform access via. identifier
This pull request fixes 9 alerts when merging f054307 into c9271c3 - view on LGTM.com fixed alerts:
|
Nice! The Travis build is still failing. I'll review when it's green, so I can just go by the tests. |
@raucao seems to be failing to get a |
This pull request fixes 9 alerts when merging 2fa86db into c9271c3 - view on LGTM.com fixed alerts:
|
@raucao seems like things are passing and green now |
This pull request fixes 9 alerts when merging a56bf94 into c9271c3 - view on LGTM.com fixed alerts:
|
This pull request fixes 9 alerts when merging 4f3db4a into c9271c3 - view on LGTM.com fixed alerts:
|
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.
Left some comments. Love that there are more tests now!
One thing I would consider when using spec syntax like "describe", is to also use spec language instead of "should". For example "it should generate a failure report" would turn into "it generates a failure report", which both removes the superfluous extra word, as well as reads more like a specification than a wish list. Just my personal opinion though.
Btw, I think this PR is more of a kredits-2
. The 3 is really a bit of a nuclear option for when it's most definitely more than 3 mediums, and usually even more than that. I had plenty of mediums that I spent more than a day working on for example. The incentive should always be to make PRs smaller (and thus easier to review and reason about) instead of slapping a 3 on ones that contain too many side quests. :)
Yeah, good suggestion. I'll do that.
OK, I am still pretty unsure of when to use which, so I'll try to remember that rule of thumb. |
Co-authored-by: Râu Cao <sebastian@kip.pe>
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.
Just some typos...
Co-authored-by: Râu Cao <sebastian@kip.pe>
Co-authored-by: Râu Cao <sebastian@kip.pe>
Co-authored-by: Râu Cao <sebastian@kip.pe>
Resolves #269