Skip to content

Move Surge token to secrets (and regenerate it) #71

@mturley

Description

@mturley

It would be nice to not have to hard-code our surge.sh token in the GitHub Actions workflows, but this is non-trivial and not a significant security risk.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions