Skip to content

Document Azure Pipelines #26

Description

@epage

Azure Pipelines supports github

Why should we document this?

  • Some users might prefer it
  • It has the potential to reduce the boiler plate, ie no more trust

Would this be recommended over Travis? Unsure, we'll have to see how things evolve and learn from experience with each service.

Should we provide configuration templates? Eventually. It'll take some iteration to determine the right level of configurability so we don't lock people in.

Metadata

Metadata

Assignees

No one assigned

    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