Skip to content

docs: Update Latest News in README.md#3790

Open
sbhavani wants to merge 1 commit intoNVIDIA:mainfrom
sbhavani:docs/readme-falcon-h1-moe-news
Open

docs: Update Latest News in README.md#3790
sbhavani wants to merge 1 commit intoNVIDIA:mainfrom
sbhavani:docs/readme-falcon-h1-moe-news

Conversation

@sbhavani
Copy link
Contributor

What does this PR do ?

add MoE technical report and Falcon-H1 blog to Latest News

⚠️ 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.

@sbhavani sbhavani added the docs-only documentation only (docs or docstrings) label Mar 10, 2026
@copy-pr-bot
Copy link

copy-pr-bot bot commented Mar 10, 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.

@svcnvidia-nemo-ci svcnvidia-nemo-ci marked this pull request as draft March 10, 2026 23:07
@github-actions
Copy link
Contributor

This PR has been automatically converted to draft because all PRs must start as drafts.

When you are ready for review, click Ready for Review to begin the review process. This will:

  1. Add the oncall reviewer (optional reviewer)
  2. Add required review teams based on your changes

See the contribution guide for more details.

@sbhavani sbhavani marked this pull request as ready for review March 10, 2026 23:09
@svcnvidia-nemo-ci svcnvidia-nemo-ci requested a review from a team March 10, 2026 23:09
@svcnvidia-nemo-ci svcnvidia-nemo-ci added docs-only documentation only (docs or docstrings) and removed docs-only documentation only (docs or docstrings) labels Mar 10, 2026
@Phlip79
Copy link
Member

Phlip79 commented Mar 11, 2026

Can we also add these links to a permanent location? Eventually, we'll delete the existing links from latest news.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-only documentation only (docs or docstrings)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants