Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Github status for google3 seems to revert itself back to a "yellow" state #30826

Closed
benlesh opened this issue Jun 3, 2019 · 2 comments
Closed

Github status for google3 seems to revert itself back to a "yellow" state #30826

benlesh opened this issue Jun 3, 2019 · 2 comments
Labels
area: build & ci Related the build and CI infrastructure of the project regression Indicates than the issue relates to something that worked in a previous version
Milestone
needsTriage

Comments

@benlesh
Copy link
Contributor

benlesh commented Jun 3, 2019

Recently, I ran into an issue where, without pushing any updates to a PR, the google3 status was reverting itself after a few minutes.

This is one PR where that was happening consistently:
#30670 (comment)
@benlesh benlesh added area: build & ci Related the build and CI infrastructure of the project severity2: inconvenient labels Jun 3, 2019
@ngbot ngbot bot added this to the needsTriage milestone Jun 3, 2019
@kara kara added regression Indicates than the issue relates to something that worked in a previous version and removed severity2: inconvenient labels Jun 3, 2019
@kara
Copy link
Contributor

kara commented Feb 28, 2020

Closing as outdated

@kara kara closed this as completed Feb 28, 2020
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area: build & ci Related the build and CI infrastructure of the project regression Indicates than the issue relates to something that worked in a previous version
Projects
None yet
Milestone
needsTriage
Development

No branches or pull requests
2 participants
@benlesh @kara