Skip to content

Start moving repositories master branch to main #90476

Closed

Description

@godofredoc

There are a number of repositories that we can migrate to use main right away:

  • cocoon
  • recipes

Migrating those two repos will give us enough information about what will be required to migrate repositories with more traffic like engine. Flutter/flutter has its own challenges and will require its own design doc.

Activity

  1. self-assigned this
    on Sep 21, 2021
  2. godofredoc commented on Sep 21, 2021

    @godofredoc
    ContributorAuthor

    GoB configurations to keep master and main in sync have already landed.

    https://flutter-review.googlesource.com/c/infra/+/18342 to move recipes to use main.

  3. godofredoc commented on Sep 22, 2021

    @godofredoc
    ContributorAuthor

    CL to use main branch in engine builders: https://flutter-review.googlesource.com/c/infra/+/18344

  4. godofredoc commented on Sep 22, 2021

    @godofredoc
    ContributorAuthor

    Start using main branch from cocoon repository: https://flutter-review.googlesource.com/c/recipes/+/18361

  5. stuartmorgan-g commented on Nov 3, 2021

    @stuartmorgan-g
    Contributor

    @godofredoc If you want to set up master->main mirroring for flutter/plugins and flutter/packages, I can start updating scripts and CI jobs as I have time; I would expect that they will be fairly straightforward repos to migrate.

  6. godofredoc commented on Nov 3, 2021

    @godofredoc
    ContributorAuthor

    Thanks @stuartmorgan, I'll send the changes for review during the day.

  7. 20 remaining items

  8. godofredoc commented on Jun 13, 2023

    @godofredoc
    ContributorAuthor

    Closing because the bug has not been updated for more than one year.

    Feel free to reopen any bugs that you believe are important but please provide updates on how to resource the fix of the bug and what can be done to prevent the issue from not getting updates for another year.

  9. github-actions commented on Jun 27, 2023

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  10. locked as resolved and limited conversation to collaborators on Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

team-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions