-
Notifications
You must be signed in to change notification settings - Fork 249
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
jpayne3506
wants to merge
38
commits into
master
Choose a base branch
from
jpayne3506/signed-fix
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this 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 likebuild-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
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
rohitams
previously approved these changes
Jul 16, 2025
miguelgoms
previously approved these changes
Jul 16, 2025
rohitams
previously approved these changes
Jul 16, 2025
miguelgoms
previously approved these changes
Jul 16, 2025
0abba8a
to
a81f4f2
Compare
a81f4f2
to
655d5cf
Compare
48d35da
to
34ecf45
Compare
bf78d77
to
5e28e22
Compare
9904015
to
574c034
Compare
d955e16
to
451a669
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change:
Addresses matching stage names.
Issue Fixed:
Requirements:
Notes: