[dont merge] visualizing diff during rebase of mbridge

[terrykong]

What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

Issues

List issues that this PR closes (syntax):

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you run the unit tests and functional tests locally? Visit our Testing Guide for how to run tests
• Did you add or update any necessary documentation? Visit our Document Development Guide for how to write, build and test the docs.

Additional Information

• ...

[github-actions]

✅ Submodule Fast-Forward Check Results

Check based on commit: 0879596 (PR #996 from yuya/adapt_megatron_bridge-rebase)

✅ Submodules that are properly updated:

Megatron-Bridge: ✅ New submodule being added
Megatron-LM: ✅ PR branch is ahead of main branch (fast-forward)

All submodule changes look good! ✨

[github-actions]

✅ Submodule Fast-Forward Check Results

Check based on commit: 092fb24 (PR #996 from yuya/adapt_megatron_bridge-rebase)

✅ Submodules that are properly updated:

Megatron-Bridge: ✅ New submodule being added
Megatron-LM: ✅ PR branch is ahead of main branch (fast-forward)

All submodule changes look good! ✨

[github-actions]

✅ Submodule Fast-Forward Check Results

Check based on commit: 1c9e78a (PR #996 from yuya/adapt_megatron_bridge-rebase)

✅ Submodules that are properly updated:

Megatron-Bridge: ✅ New submodule being added
Megatron-LM: ✅ PR branch is ahead of main branch (fast-forward)

All submodule changes look good! ✨

[terrykong]

opened a PR to update upstream branch: NVIDIA-NeMo/Megatron-Bridge#496

will test this branch, if it looks good i'll force push to #905

[terrykong]

closing. this branch has served it's purposes and i've forced pushed against the orig branch