Skip to content

Allow user to specify deploy key #6

@stefangary

Description

@stefangary

Currently the ML repos approach assumes that:

  1. only the ML archive repo will be pushed to
  2. so only that repo has a deploy key and
  3. the deploy key is named based on the repo.

It would be better to allow the workflow to have a boolean on each repo whether or not it needs a key and if it does, specify the key name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions