[MINOR] Update repository references from incubator-gluten to gluten for TLP graduation of gluten#3633
Closed
SteNicholas wants to merge 1 commit intoapache:mainfrom
Closed
[MINOR] Update repository references from incubator-gluten to gluten for TLP graduation of gluten#3633SteNicholas wants to merge 1 commit intoapache:mainfrom
SteNicholas wants to merge 1 commit intoapache:mainfrom
Conversation
…for TLP graduation of gluten
RexXiong
approved these changes
Mar 18, 2026
eolivelli
approved these changes
Mar 18, 2026
Member
Author
|
Merged to main(v0.7.0). |
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
3 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.
What changes were proposed in this pull request?
Update repository references from incubator-gluten to gluten for TLP graduation of gluten.
Why are the changes needed?
Apache Gluten has already TLP graduated, which should update repository references.
Does this PR resolve a correctness bug?
No.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No.