Sync settings for archived repositories#13
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Temporarily unarchived 12 previously archived repositories, imported them into Terraform state, applied the standard settings (labels, repo config, branch protection, vulnerability alerts, dependabot security updates, secret scanning), then removed them from state again so they can be safely re-archived.
Affected repositories:
covid-19-data-collector,data-driven-food-value-chain,data-engineering,data-mining,foundations-of-databases,interactive-and-explainable-ai-design,introduction-to-machine-learning,master-thesis,natural-language-processing,social-network-analysis-for-data-scientists,statistics-bootcamp,statistics-for-data-scientists.Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
The tfvars file is unchanged — only the state file is updated to reflect drift in the
first-interactionrepo (label URLs populated, primary language detected, status check context added).Does this PR introduce a user-facing change?: