Update development-pw submod refs to point to their development branches - #271
Open
cmaynard-ngwpc wants to merge 1 commit into
Open
Update development-pw submod refs to point to their development branches#271cmaynard-ngwpc wants to merge 1 commit into
cmaynard-ngwpc wants to merge 1 commit into
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
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.
Point both the ngen
developmentand the ngendevelopment-pwbranches to the submoduledevelopmentbranches.As of the formal delivery to the testers on 8/19/26, we are no longer updating
development-pwbranches for repositories that don't have differences between theirdevelopmentanddevelopment-pwbranches for deployments to AWS vs PW.ngendoes have differences, so updates to its codebase need to be mirrored in both branches, but all the submodule references should point to thedevelopmentbranch in the submodule repository.