Skip to content

remove legacy Bert code#4204

Merged
dimapihtar merged 1 commit intoNVIDIA:mainfrom
dimapihtar:remove_legacy_bert
Apr 13, 2026
Merged

remove legacy Bert code#4204
dimapihtar merged 1 commit intoNVIDIA:mainfrom
dimapihtar:remove_legacy_bert

Conversation

@dimapihtar
Copy link
Copy Markdown
Contributor

@dimapihtar dimapihtar commented Apr 8, 2026

What does this PR do ?

Removes legacy Bert code, classification.py & multiple_choice.py as a part of MLM code cleanup.

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

Contribution process

Pre-checks

  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot bot commented Apr 8, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@dimapihtar dimapihtar marked this pull request as ready for review April 8, 2026 13:43
@svcnvidia-nemo-ci svcnvidia-nemo-ci requested a review from a team April 8, 2026 13:43
@dimapihtar
Copy link
Copy Markdown
Contributor Author

/ok to test 58a123f

@dimapihtar dimapihtar added this pull request to the merge queue Apr 13, 2026
@svcnvidia-nemo-ci
Copy link
Copy Markdown

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/24336909593

@svcnvidia-nemo-ci
Copy link
Copy Markdown

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/24339637376

Merged via the queue into NVIDIA:main with commit 7f8f37e Apr 13, 2026
67 checks passed
@dimapihtar dimapihtar deleted the remove_legacy_bert branch April 13, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants