Skip to content

Do not block cherry picks on release branches because master is red #173966

@reidbaker

Description

@reidbaker

Help us understand the severity of this issue

  • breakage; unable to contribute or trigger builds will no workarounds
  • inconvenient workarounds exist, but significant effort required
  • needed for a Flutter team-wide priority (already agreed upon)
  • nice-to-have; none of the above

What do you need help with

In pr #173869 autosubmit was added but not landed because the tree was red. This pr was a modification of a release branch which probably should not be blocked by a red master tree.

Was able to work around with the emergency label.

Metadata

Metadata

Assignees

No one assigned

    Labels

    r: invalidIssue is closed as not validteam-infraOwned by Infrastructure team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions