chore: Migration: merge Construct-X custom changes into Tractus-X fork baseline#1
Open
devajipatil wants to merge 6 commits intomainfrom
Open
chore: Migration: merge Construct-X custom changes into Tractus-X fork baseline#1devajipatil wants to merge 6 commits intomainfrom
devajipatil wants to merge 6 commits intomainfrom
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
2 participants
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.
Description:
This PR migrates the existing Construct-X frontend customizations from the legacy repository into the newly created fork of the Tractus-X portal-frontend.
Context:
The previous Construct-X repository was not created as a GitHub fork, which made upstream synchronization difficult. A fresh fork has now been created from the Tractus-X upstream, and this PR merges the downstream Construct-X changes on top of the upstream baseline.
Scope of changes:
Merge of legacy branch feature/construct-x into fork main
Preservation of Construct-X specific configurations, UI adjustments, and build changes
Alignment with upstream Tractus-X repository history to enable future upstream sync
Impact / Risk:
Large diff expected due to repository lineage merge
Requires full frontend build validation and staging deployment testing
No functional changes intended beyond preserving existing Construct-X behavior
Validation plan:
Verify successful CI build
Build container image from fork repository
Deploy to staging environment
Test portal login, navigation, assets, wallet, and contract flows
Follow-up:
After merge, downstream sync with upstream Tractus-X will be performed using standard fork update strategy.