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

Add go-ds-badger4 to github-mgmt #174

Closed
wants to merge 3 commits into from
Closed

Add go-ds-badger4 to github-mgmt #174

wants to merge 3 commits into from

Conversation

hsanjuan
Copy link

@hsanjuan hsanjuan commented Oct 6, 2023

Summary

Add go-ds-badger4 to github-mgmt

Why do you need this?

Consistency with previous versions.

What else do we need to know?

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

@hsanjuan hsanjuan requested review from a team as code owners October 6, 2023 14:54
@hsanjuan hsanjuan requested a review from galargh October 6, 2023 14:54
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2023

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

Terraform plans

ipfs

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

Terraform will perform the following actions:

  # github_branch_protection.this["go-ds-badger4:master"] will be created
  + resource "github_branch_protection" "this" {
      + allows_deletions                = false
      + allows_force_pushes             = false
      + blocks_creations                = false
      + enforce_admins                  = false
      + id                              = (known after apply)
      + lock_branch                     = false
      + pattern                         = "master"
      + repository_id                   = (known after apply)
      + require_conversation_resolution = false
      + require_signed_commits          = false
      + required_linear_history         = false
    }

  # github_repository.this["go-ds-badger4"] will be created
  + resource "github_repository" "this" {
      + allow_auto_merge            = false
      + allow_merge_commit          = true
      + allow_rebase_merge          = true
      + allow_squash_merge          = true
      + allow_update_branch         = false
      + archived                    = false
      + default_branch              = "master"
      + delete_branch_on_merge      = false
      + description                 = "Datastore implementation using Badger v4 as backend. "
      + etag                        = (known after apply)
      + full_name                   = (known after apply)
      + git_clone_url               = (known after apply)
      + has_discussions             = false
      + html_url                    = (known after apply)
      + http_clone_url              = (known after apply)
      + id                          = (known after apply)
      + merge_commit_message        = "PR_TITLE"
      + merge_commit_title          = "MERGE_MESSAGE"
      + name                        = "go-ds-badger4"
      + node_id                     = (known after apply)
      + private                     = (known after apply)
      + repo_id                     = (known after apply)
      + squash_merge_commit_message = "COMMIT_MESSAGES"
      + squash_merge_commit_title   = "COMMIT_OR_PR_TITLE"
      + ssh_clone_url               = (known after apply)
      + svn_url                     = (known after apply)
      + visibility                  = "public"

      + security_and_analysis {

          + secret_scanning {
              + status = "enabled"
            }

          + secret_scanning_push_protection {
              + status = "enabled"
            }
        }
    }

  # github_repository.this["helia-docker"] will be updated in-place
  ~ resource "github_repository" "this" {
        id                          = "helia-docker"
        name                        = "helia-docker"
        # (32 unchanged attributes hidden)

      ~ security_and_analysis {

          ~ secret_scanning {
              ~ status = "disabled" -> "enabled"
            }

          ~ secret_scanning_push_protection {
              ~ status = "disabled" -> "enabled"
            }
        }
    }

  # github_repository_collaborator.this["go-ds-badger4:web3-bot"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "go-ds-badger4"
      + username                    = "web3-bot"
    }

  # github_repository_file.this["go-ds-badger4/.github/workflows/stale.yml"] will be created
  + resource "github_repository_file" "this" {
      + branch              = "master"
      + commit_author       = "GitHub"
      + commit_email        = "[email protected]"
      + commit_message      = "chore: Update .github/workflows/stale.yml [skip ci]"
      + commit_sha          = (known after apply)
      + content             = <<-EOT
            name: Close and mark stale issue
            
            on:
              schedule:
                - cron: '0 0 * * *'
            
            permissions:
              issues: write
              pull-requests: write
            
            jobs:
              stale:
                uses: pl-strflt/.github/.github/workflows/[email protected]
        EOT
      + file                = ".github/workflows/stale.yml"
      + id                  = (known after apply)
      + overwrite_on_create = false
      + ref                 = (known after apply)
      + repository          = "go-ds-badger4"
      + sha                 = (known after apply)
    }

  # github_repository_file.this["helia-docker/.github/workflows/stale.yml"] will be created
  + resource "github_repository_file" "this" {
      + branch              = "main"
      + commit_author       = "GitHub"
      + commit_email        = "[email protected]"
      + commit_message      = "chore: Update .github/workflows/stale.yml [skip ci]"
      + commit_sha          = (known after apply)
      + content             = <<-EOT
            name: Close and mark stale issue
            
            on:
              schedule:
                - cron: '0 0 * * *'
            
            permissions:
              issues: write
              pull-requests: write
            
            jobs:
              stale:
                uses: pl-strflt/.github/.github/workflows/[email protected]
        EOT
      + file                = ".github/workflows/stale.yml"
      + id                  = (known after apply)
      + overwrite_on_create = false
      + ref                 = (known after apply)
      + repository          = "helia-docker"
      + sha                 = (known after apply)
    }

  # github_repository_file.this["rainbow/.github/workflows/stale.yml"] will be updated in-place
  ~ resource "github_repository_file" "this" {
      + commit_author       = "GitHub"
      + commit_email        = "[email protected]"
      ~ commit_message      = "Update .github/workflows/stale.yml" -> "chore: Update .github/workflows/stale.yml [skip ci]"
        id                  = "rainbow/.github/workflows/stale.yml"
        # (8 unchanged attributes hidden)
    }

Plan: 5 to add, 2 to change, 0 to destroy.

@galargh
Copy link
Contributor

galargh commented Oct 9, 2023

Hi! Thanks for creating the PR. For repositories (or any other changes for that matter) created manually/outside GitHub Management, they way to import them to this repo is to run the Synchronization workflow. In this case, the workflow has ran automatically on schedule (each Sunday) and pulled in your repo. You can see the relevant commit here - 85d685c

@galargh galargh closed this Oct 9, 2023
@hsanjuan hsanjuan deleted the go-ds-badger4 branch October 11, 2023 13:25
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.

2 participants