Renamed many CRD and Profile things and now Profiles are generated per profile release (e.g. RVA20.pdf, RVA22,pdf) #249
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
…r profile release (e.g. RVA20.pdf, RVA22,pdf)
Base automatically changed from
238-missing-recommendations-in-profiles-and-add-extra_notes-to-replace-excluded-extensions
to
main
November 7, 2024 18:53
…rofile-pdf-for-each-profile-family-release-eg-rva23-not-one-pdf-for-all-profiles-in-a-family-eg-rva
dhower-qc
approved these changes
Nov 7, 2024
james-ball-qualcomm
deleted the
237-create-separate-profile-pdf-for-each-profile-family-release-eg-rva23-not-one-pdf-for-all-profiles-in-a-family-eg-rva
branch
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.
Fixes issue #237 (Create separate profile PDF for each profile family release (e.g., RVA23) not one PDF for all profiles in a family (e.g., RVA)