Skip to content

feat: default archive_on_destroy to true and has_downloads to false - #14

Merged
josmo merged 2 commits into
mainfrom
feat/archive-on-destroy-default
Aug 16, 2026
Merged

feat: default archive_on_destroy to true and has_downloads to false#14
josmo merged 2 commits into
mainfrom
feat/archive-on-destroy-default

Conversation

@josmo

@josmo josmo commented Aug 16, 2026

Copy link
Copy Markdown
Member

Archiving a repository on destroy is safer than permanently deleting it. Consumers can still opt out per-repo with archive_on_destroy = false. Also set has_downloads to false (deprecated ages ago)

What & why

Safer to have archive on destroy true by default

Checklist

  • PR title follows Conventional Commits (it is linted)
  • terraform fmt -recursive is clean
  • pre-commit run --all-files passes (docs regenerated if inputs/outputs/resources changed)
  • terraform test passes for any submodule I changed
  • Breaking input changes are described below (pre-1.0)

Breaking changes

default to archive

Archiving a repository on destroy is safer than permanently deleting it.
Consumers can still opt out per-repo with archive_on_destroy = false.
@josmo
josmo requested a review from a team as a code owner August 16, 2026 18:50
@josmo josmo changed the title feat: default archive_on_destroy to true feat: default archive_on_destroy to true and has_downloads to false Aug 16, 2026
The GitHub Downloads section is a deprecated legacy feature superseded by
Releases. Defaulting it off matches GitHub's effective default and avoids
spurious drift on existing repositories.
@josmo
josmo merged commit 529fa30 into main Aug 16, 2026
6 checks passed
@josmo
josmo deleted the feat/archive-on-destroy-default branch August 16, 2026 18:56
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.

1 participant