Draft
Conversation
this should help teams manage breaking changes and also ensure that they can take whatever version required for their specific project to work Signed-off-by: Sean Simmons <ssimmons@progress.com>
There was a problem hiding this comment.
Pull request overview
Adds documentation and workflow wiring intended to support independently pinning reusable “sub-workflow” scan versions so teams can adopt updates incrementally and avoid breaking changes across their CI/CD pipelines.
Changes:
- Documented “Sub-Workflow Versioning” and listed new
*-versioninputs in pipeline reference and usage guides. - Updated the CI reusable workflow to reference scan workflows using
@${{ inputs.*-version }}refs. - Updated the CI stub workflow examples to show optional version pinning inputs.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
PIPELINE-REFERENCE.md |
Adds a new “Sub-Workflow Versioning” section and updates workflow mapping docs to include version inputs. |
HOW-TO-USE.md |
Adds examples showing how to pin individual scan versions. |
.github/workflows/stubs/ci-main-pull-request-stub.yml |
Updates stub to document optional *-version inputs for pinning. |
.github/workflows/ci-main-pull-request.yml |
Attempts to make reusable-workflow refs configurable via new *-version inputs. |
Signed-off-by: Sean Simmons <ssimmons@progress.com>
Signed-off-by: Sean Simmons <ssimmons@progress.com>
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
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.
this should help teams manage breaking changes and also ensure that they can take whatever version required for their specific project to work
Description
There are many times where teams need to merge or update their specific scans. Versioning these options now are able to work better within the context of their ci/cd pipelines. This will enable folks to take in changes where they see fit and or create "versions" that they need specifically.
The goal here is to prevent breakages when new versions are created.
Related Issue
Types of changes
Checklist:
Gemfile.lockhas changed, I have used--conservativeto do it and included the full output in the Description above.