Skip to content

fix: change build stage name to intent #3829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 38 commits into
base: master
Choose a base branch
from

Conversation

jpayne3506
Copy link
Contributor

Reason for Change:

Addresses matching stage names.

Issue Fixed:

Requirements:

Notes:

@Copilot Copilot AI review requested due to automatic review settings July 16, 2025 00:59
@jpayne3506 jpayne3506 added fix Fixes something. ci Infra or tooling. labels Jul 16, 2025
@jpayne3506 jpayne3506 requested a review from a team as a code owner July 16, 2025 00:59
@jpayne3506 jpayne3506 requested a review from BeegiiK July 16, 2025 00:59
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the stages in the run-pipeline YAML to better reflect their intent by renaming the build stages.

  • Renamed the PR build stage key and updated its displayName
  • Renamed the release build stage key and updated its displayName
Comments suppressed due to low confidence (2)

.pipelines/run-pipeline.yaml:47

  • [nitpick] Stage key build_acndevops uses snake_case and may not align with your project’s naming conventions; consider using kebab-case (e.g., build-acndevops) or a clearer identifier like build-pr.
- stage: build_acndevops

.pipelines/run-pipeline.yaml:205

  • [nitpick] Stage key build_release deviates from a consistent naming pattern; consider using kebab-case (e.g., build-release) or aligning it with other stage identifiers.
- stage: build_release

@jpayne3506
Copy link
Contributor Author

/azp run Azure Container Networking PR

@jpayne3506 jpayne3506 self-assigned this Jul 16, 2025
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

rohitams
rohitams previously approved these changes Jul 16, 2025
miguelgoms
miguelgoms previously approved these changes Jul 16, 2025
rohitams
rohitams previously approved these changes Jul 16, 2025
@jpayne3506 jpayne3506 dismissed stale reviews from rohitams and miguelgoms via e93cb70 July 16, 2025 15:50
miguelgoms
miguelgoms previously approved these changes Jul 16, 2025
@jpayne3506 jpayne3506 force-pushed the jpayne3506/signed-fix branch from a81f4f2 to 655d5cf Compare July 16, 2025 21:03
@jpayne3506 jpayne3506 force-pushed the jpayne3506/signed-fix branch 4 times, most recently from 48d35da to 34ecf45 Compare July 17, 2025 21:06
@jpayne3506 jpayne3506 force-pushed the jpayne3506/signed-fix branch from bf78d77 to 5e28e22 Compare July 18, 2025 00:37
@jpayne3506 jpayne3506 force-pushed the jpayne3506/signed-fix branch from 9904015 to 574c034 Compare July 18, 2025 03:36
@jpayne3506 jpayne3506 force-pushed the jpayne3506/signed-fix branch from d955e16 to 451a669 Compare July 18, 2025 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Infra or tooling. fix Fixes something.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants