Skip to content

Make dry-run publish steps' labeling more explicit #208

Description

@threexc

From #204 (comment):

not strictly related to this PR, but what about having a ./.github/workflows/deploy.yml workflow that would contains this to avoid copying it in each individual workflow?

The other benefit is that inside this file we could do something like:

  • name: Deploy${{ github.ref != 'refs/heads/main' && ' (dry run)' || '' }}
    uses: ./.github/actions/deploy
    with:
    dry-run: ${{ github.ref != 'refs/heads/main' }}

So the name of the job will actually contain "(dry run)" . Right now, we have the impression that the publish job succeeded and correctly uploaded file on the registry


Further deploy changes probably aren't worth the effort, but taking Julien's suggestion to make the dry-run labeling more explicit would be helpful for our PRs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestgood first issueGood for newcomersinfrastructureWork related to repo automation, such as nightly builds, PR tests, and other related topics

    Type

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions