Skip to content

Actions: Remove unused workflows #1319

Open
1 of 1 issue completed
Open

Description

@AkhileshNegi

Is your feature request related to a problem?
Image
The Actions sidebar displays several unused deployment workflows, causing confusion about which one is for staging. The dev workflows created for KMS testing are no longer necessary.

Describe the solution you'd like

  • Remove/disable the following unused dev workflows from the Actions UI:
    • Deploy Kaapi dev to EC2 (.github/workflows/deploy-dev.yml)
    • Deploy Kaapi dev-staging to EC2 (.github/workflows/deploy-dev-staging.yml)
  • Delete their files from any stale branch or delete the stale branch itself.
  • Retain the ECS workflows (Deploy Kaapi to ECS Staging, Deploy Kaapi to ECS Production).
  • Keep Deploy Kaapi to Staging EC2 (deploy-staging.yml) as it is currently in use.

Activity

  1. changed the title [-]Infra: Remove unused dev deployment workflows[/-] [+]Actions: Remove unused workflows[/+] on Nov 2, 2026
  2. vprashrex commented on Nov 2, 2026

    @vprashrex
    Collaborator

    I had already deleted deploy-dev.yml and deploy-dev-staging.yml a while back, so they're not on main or any remote branch. The ECS workflows and deploy-staging.yml are untouched.

    The two entries still show in the Actions sidebar because GitHub keeps deleted workflows registered. Only the GitHub-side cleanup is left (disable them, or delete their old runs so they drop off the list).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions