Fix compare to master files

[michaltk]

Comparing with master files does not seem to be working bec:

1. When checking if there are master files here, the destructed variable master is being used for this check. That variable was set before setting master on it. Fixed this by moving the destructing of files to after master was already set on it.
2. In the setBuildStatus function, the name of the params of the function do not match the object that is being sent it. Fixed the names of it.

[siddharthkp]

@michaltk Hey!

Thanks for the pull request! I'll test this out tomorrow

[karanjthakkar]

Hey @michaltk good catch! Sorry about this! This was accidentally introduced in these commits: 568194d 9e4880be3acaa11fd88ef8f219252a3836f18460and has been there from v0.14.3 onwards.

[karanjthakkar]

@SaraVieira Can we publish a new version whenever you are free? I'm not sure if this marks the test as failing in Github UI but in our store UI, the master column appears empty:

[SaraVieira]

I don't have access to publish the new UI on now , only @siddharthkp has :(

[karanjthakkar]

@SaraVieira this is unrelated to the other PR. Here I'm talking about publishing a new version to npm with the fix. It doesnt need the store redeploy.

[SaraVieira]

@karanjthakkar I did one yesterday :)

[siddharthkp]

Hi! My spidey senses tingled. How can I help 😄

[karanjthakkar]

@SaraVieira Did you cherry pick the fix in this PR too? If not, we'll need to push another release with this fix.

[SaraVieira]

@karanjthakkar No I didn't , please push another release and I will publish it

[karanjthakkar]

@SaraVieira Done. Pushed v0.15.2

[SaraVieira]

@karanjthakkar Published 🎉

[karanjthakkar]

Awesome!

Thanks again for bringing this to our attention and fixing this, @michaltk! 🥇