Skip to content
This repository was archived by the owner on Jan 19, 2024. It is now read-only.

Conversation

@ocombe
Copy link
Contributor

@ocombe ocombe commented Feb 28, 2019

No description provided.

Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you please update the comment message with info about this change? and can you please do that for future PRs as well?

It's very difficult to review PRs without description and especially if they don't add new specs.

otherwise lgtm... I guess (since there are not tests it's hard to be confident)...

We were updating the g3status when the merge label was added. This meant that if a g3sync had updated the status, it was overwritten.
With this PR we now only update the g3status on sync (new commit or force push) or when the g3status is missing.
@ocombe ocombe merged commit 769547d into angular:master Feb 28, 2019
@ocombe ocombe deleted the fix/g3status branch February 28, 2019 08:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants