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.

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

Archive unused repos #67

Merged
merged 7 commits into from
May 6, 2024
Merged

Conversation

BigLep
Copy link
Contributor

@BigLep BigLep commented Feb 8, 2024

Noticed some repos that should probably be archived.

Summary

The are some repos that no longer look to be used. They were identified while going through #65. I acted in #66, but want to apply this subset of changes to master and also remove permissions of the archived repos.

Why do you need this?

Not needed, but it's for declutter.
It's also not a one-way door. Repos can be unarchived if needed.

What else do we need to know?

None

DRI: myself

Reviewer's Checklist

  • It is clear where the request is coming from (if unsure, ask)
  • All the automated checks passed
  • The YAML changes reflect the summary of the request
  • The Terraform plan posted as a comment reflects the summary of the request

@BigLep BigLep requested review from a team as code owners February 8, 2024 22:28
@BigLep BigLep mentioned this pull request Feb 8, 2024
4 tasks
Copy link
Member

@rvagg rvagg left a comment

Choose a reason for hiding this comment

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

approve in concept but something about the config needs to change, I think maybe it doesn't like empty users? @galargh probably either something for you to fix in the permissions checking code or something obvious to fix in the config here?

@BigLep
Copy link
Contributor Author

BigLep commented Feb 9, 2024

Thanks @rvagg ! I should have checked to make sure the checks pass first. We'll figure out how to get that passing and then merge.

github/ipld.yml Outdated Show resolved Hide resolved
Copy link
Contributor

github-actions bot commented May 6, 2024

The following access changes will be introduced as a result of applying the plan:

Access Changes
User achingbrain:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User aschmahmann:
  - will lose admin permission to edelweiss
  - will lose pull permission to go-selector-store
  - will lose admin permission to js-ipld-format-to-blockcodec
User biglep:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User galargh:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User guseggert:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User jorropo:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User laurentsenta:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User lidel:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User petar:
  - will lose admin permission to edelweiss
User rvagg:
  - will lose pull permission to edelweiss
  - will lose pull permission to go-selector-store
  - will lose pull permission to js-ipld-format-to-blockcodec
User stebalien:
  - will lose admin permission to edelweiss
  - will lose admin permission to js-ipld-format-to-blockcodec
User vmx:
  - will lose pull permission to edelweiss
  - will lose pull permission to go-selector-store
  - will lose pull permission to js-ipld-format-to-blockcodec
User web3-bot:
  - will lose push permission to edelweiss
User willscott:
  - will lose pull permission to edelweiss
  - will lose pull permission to go-selector-store
  - will lose pull permission to js-ipld-format-to-blockcodec

Copy link
Contributor

github-actions bot commented May 6, 2024

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

ipld

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # github_repository.this["edelweiss"] will be updated in-place
  ~ resource "github_repository" "this" {
      ~ archived                    = false -> true
        id                          = "edelweiss"
        name                        = "edelweiss"
        # (32 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # github_repository.this["go-selector-store"] will be updated in-place
  ~ resource "github_repository" "this" {
      ~ archived                    = false -> true
        id                          = "go-selector-store"
        name                        = "go-selector-store"
        # (32 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # github_repository.this["js-ipld-format-to-blockcodec"] will be updated in-place
  ~ resource "github_repository" "this" {
      ~ archived                    = false -> true
        id                          = "js-ipld-format-to-blockcodec"
        name                        = "js-ipld-format-to-blockcodec"
        # (32 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

Plan: 0 to add, 3 to change, 0 to destroy.

@galargh galargh merged commit 90ebd77 into master May 6, 2024
6 checks passed
@galargh galargh deleted the from-biglep-archive-repos-2024q1-attempt2 branch May 6, 2024 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants