Skip to content

Create reusable workflow_call templates for module CI/CD #1

Description

@lipkau

Problem

Complex CI/release workflow logic is duplicated across AtlassianPS module repositories, which causes drift and makes cross-repo hardening slow and error-prone.

Proposal

Create reusable workflow_call templates in AtlassianPS.Standards for module CI, release, and policy checks. Keep repo-local wrappers thin and repository-specific.

Acceptance criteria

  • AtlassianPS.Standards ships reusable workflows for CI and release with documented inputs/outputs.
  • JiraPS is migrated as the pilot consumer using thin wrapper workflows.
  • A policy check exists that flags deprecated action references and mutable @master action pins.
  • Migration guidance documents how remaining repos adopt the reusable workflows incrementally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    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