Rename project-stable-mir

[makai410]

cc @celinval

[github-actions]

Dry-run check results

[WARN  rust_team::sync] sync-team is running in dry mode, no changes will be applied.
[INFO  rust_team::sync] synchronizing crates-io
[INFO  rust_team::sync] synchronizing github
[INFO  rust_team::sync] 💻 Team Diffs:
    ➕ Creating team:
      Org: rust-lang
      Name: project-rustc-public
      Description: Managed by the rust-lang/team repository.
      Privacy: closed
      Members:
        celinval: member
        makai410: member
        oli-obk: member
        scottmcm: member
    ❌ Deleting team 'rust-lang/project-stable-mir'
    💻 Repo Diffs:
    📝 Editing repo 'rust-lang/rust':
      Permission Changes:
        Giving team 'project-rustc-public' write permission
        Removing team 'project-stable-mir''s write permission 
    ➕ Creating repo:
      Org: rust-lang
      Name: rustc_public
      Description: Define compiler intermediate representation usable by external tools
      Homepage: None
      Auto-merge: true
      Permissions:
        Giving team 'project-rustc-public' write permission
        Giving user 'rustbot' write permission
      Rulesets:
        main
            Include Branches: ["refs/heads/main"]
            Required approvals: 1
      Environments:
        - github-pages
      App Installations:

[makai410]

What would the bot do to the repo? Rename or create a new one? What we want is to rename the project-stable-mir repo to rustc_public.

[celinval]

Sweet! Thanks for following up on this.

BTW, I think we'll also need to update the triagebot: https://github.com/rust-lang/rust/blob/9e2abe0c6ab27fcbb95c30695188a75776e2feb1/triagebot.toml#L1642

[celinval]

Maybe let's just call it Rustc Public Project Group. I think there was a librarification effort that predates rustc_public, which someone called it out during the rust week.

[makai410]

I think you probably mean this one: https://smallcultfollowing.com/babysteps/blog/2020/04/09/libraryification/ :D Makes sense, let me fix that

[Kobzol]

Renaming the repo has to be done manually with an onfra admin, team would just create a new one (this PR will be merged right after the rename).

[marcoieni]

Renaming the repo has to be done manually with an onfra admin, team would just create a new one (this PR will be merged right after the rename).

I renamed the repo and I'm merging this PR. I have to say this process is quite scary and error prone. Eg if I make a typo in the repo rename, the repo gets deleted 😅

I like more the terraform approach that keeps track of resources and detects when something gets renamed