Skip to content
This repository was archived by the owner on Jun 27, 2025. It is now read-only.

ci: add new pr title requirement workflow - #1

Open
pascal-arevalo wants to merge 1 commit into
mainfrom
feature/pr-title-ci
Open

ci: add new pr title requirement workflow#1
pascal-arevalo wants to merge 1 commit into
mainfrom
feature/pr-title-ci

Conversation

@pascal-arevalo

@pascal-arevalo pascal-arevalo commented Jun 25, 2025

Copy link
Copy Markdown

Rationale

Introduces a GitHub Actions workflow to enforce a standardized format for Pull Request titles across the organization.

All PR titles must follow the conventional commits specification and additionally end with AB#<HU-ID>, where <HU-ID> is the Azure DevOps task ID associated with the work. For example:

feat(routes): add new /users route to merchant users [AB#123](https://dev.azure.com/wompi-co/e4538663-13b6-40f0-948d-94024707b88f/_workitems/edit/123)

Discussion

N/A

Affected Components

  • .github/workflows/pr-title.yaml - Adds new workflow

Security Concerns

N/A

Impact Documentation

The authorized party responsible for applying/releasing approved changes to the system must follow these steps:

  1. Identify clearly the components affected in the deployment
  • A new GitHub actions to enforce internal guidelines is added, no infrastructure or software is modified.
  1. According to the components impacted identify in Wompi value chain the improvements proposed:
    1. Transactional Processing
    • N/A
    1. Fraud Prevention
    • N/A
    1. Cybersecurity
      1. Threat Prevention
      • N/A
      1. Vulnerability Fixing
      • N/A
    2. Vendor specific
      1. New vendor onboarding or integration
      • N/A
      1. Obsolete vendor removal and resources deletion
      • N/A
      1. Shared responsibility model compliance (e.g. AWS)
      • N/A
  2. Sign off with a conclusion and compliance with all applicable guidelines

This change introduces a standardized process for PR title formatting, ensuring consistency and traceability across the organization. The workflow does not impact infrastructure or application code, and complies with all internal guidelines.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants