✨ Transform to MTA pointer-based build repository #32
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
djzager
force-pushed
the
feature/mta-pointer-build
branch
2 times, most recently
from
603cd18 to
1da3aa2
Compare
|
@djzager If possible, can you separate out deletions and the actual stuff into separate commits? |
This repository will no longer contain the source code for the MTA extensions. Instead, it will pull upstream konveyor/editor-extensions source code and apply MTA branding during the build process. The source code is removed to make way for the new pointer-based build system that references upstream by SHA.
This commit introduces a new build approach where we: - Reference upstream konveyor/editor-extensions by SHA - Pull upstream source at build time - Apply MTA branding via scripts during prebuild - Build extensions with MTA-specific configuration Key files: - mta-build.yaml: Configuration for upstream ref and branding - scripts/pull-upstream.js: Clones and prepares upstream workspace - scripts/apply-branding.js: Transforms package.json files for MTA - scripts/update-upstream.sh: Helper to update upstream SHA - .github/workflows/ci.yml: Build workflow using pointer-based approach This approach allows us to track upstream changes while maintaining MTA-specific branding and configuration without duplicating source.
djzager
force-pushed
the
feature/mta-pointer-build
branch
from
1da3aa2 to
a4094cf
Compare
pranavgaikwad
requested changes
Jan 14, 2026
| "linux-arm64": "mta-analyzer-rpc", | ||
| "darwin-x64": "darwin-mta-analyzer-rpc", | ||
| "darwin-arm64": "darwin-mta-analyzer-rpc", | ||
| "win32-x64": "windows-mta-analyzer-rpc", |
| path: .upstream-workspace/dist/*.vsix | ||
| retention-days: 30 | ||
|
|
||
| - name: Upload workspace for debugging |
There was a problem hiding this comment.
does it make sense to upload artifacts all the time? I am wondering in a scenario where the build is successful but not quite right?
djzager
added
bug
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.
No description provided.