Skip to content

Remove or rename push-candidate command #65

Description

@andreasabel

The hackage-cli command push-candidate is in the way of push-cabal when tab-completing hackage-cli push<TAB> or even hackage-cli push-ca<TAB>. Also, I never use it and I do not see what its purpose is when we have cabal upload.

I propose to remove it.

Alternatively, one could just move it into a legacy command group so that it is only available as hackage-cli legacy push-candidate.
Or rename it to candidate-push.

If you are a user of push-candidate, please leave a comment here how you use this feature and why it is important.
@hvr @phadej @gbaz @hesselink @bergmark @endgame @davean @Bodigrim @andreabedini @ulysses4ever @pbrisbin @sjakobi @vaibhavsagar

Activity

  1. andreabedini commented on Oct 9, 2023

    @andreabedini

    I don't use push-candidate but having candidate-push and push-cabal would look a bit funny to me (and triggers my OCD 😂).

    Rename push-candidate to push-version-candidate? Maybe push/pull-cabal could also be push/pull-revision (matching the existing check-revision).

  2. added this to the 0.2 milestone on Jan 26, 2024
  3. added a commit that references this issue on Jan 26, 2024
    807b9c8
  4. added a commit that references this issue on Sep 1, 2025
    6d9fd6b
  5. phadej commented on Apr 15, 2026

    @phadej
    Collaborator

    I think push-candidate predates cabal upload uploading candidates (by default or at all). IMO whole command can be just removed.

  6. added a commit that references this issue on Jul 1, 2026
    40d20ab
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions