Skip to content

chore: remove the .github-old directory - #60

Merged
cigamit merged 1 commit into
ctrliq:develfrom
blaipr:chore/remove-the-github-old-directory
Sep 17, 2026
Merged

cigamit merged 1 commit into
ctrliq:develfrom
blaipr:chore/remove-the-github-old-directory

Conversation

@blaipr

@blaipr blaipr commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

14 files GitHub never reads. It only looks in .github, nothing in the repository references .github-old, and the live .github already carries the workflows that matter.

What is in there

Upstream's, and stale:

  • ISSUE_TEMPLATE/bug_report.yml points at ansible/awx-operator/issues for duplicates, says "I understand that the AWX Operator is open source software", and asks for an awx-operator-version
  • workflows/publish-operator-hub.yaml defaults its fork to awx-auto
  • workflows/reusable-nox.yml, ci.yaml, feature.yml, the label workflows: a nox-based CI this repository does not use

It is the largest remaining lump of awx in the repo, and none of it runs.

One thing worth saying out loud

Two of these have no counterpart under .github: the issue templates and PULL_REQUEST_TEMPLATE.md. So this repository has neither, and has not since the directory was renamed.

Deleting them does not take anything away that was working. But reviving them means writing Ascender ones, not restoring these, which ask a reporter for the version of a different product. Worth a follow-up if you want templates back.

Everything stays in the history.

Fourteen files GitHub never reads. It only looks in .github, nothing in
the repository references .github-old, and the live .github already has
the workflows that matter.

What is in there is upstream's: issue templates pointing at
ansible/awx-operator for duplicates and asking for an awx-operator
version, a publish workflow defaulting to an awx-auto fork, and a nox
based CI that this repository does not use. It is the largest remaining
lump of awx here, and none of it runs.

Two of the files have no counterpart under .github, which is worth
saying rather than leaving to be discovered: the issue templates and the
pull request template. This repository therefore has none, and has not
had since the directory was renamed. Reviving them means writing Ascender
ones rather than restoring these, which ask a reporter for the version of
a different product.

Everything stays in the history.
@ciq-it-service-account

ciq-it-service-account commented Sep 17, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cigamit cigamit self-assigned this Sep 17, 2026
@cigamit
cigamit merged commit 649823e into ctrliq:devel Sep 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants