Change oncall team name (NVIDIA#2861)

Author: Phlip79

.github/ISSUE_TEMPLATE/bug_report.md

@@ -9,7 +9,7 @@ assignees: ''
 
 **Describe the bug**
 
-A clear and concise description of what the bug is. Tag the [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall) 
+A clear and concise description of what the bug is. Tag the [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall) 
 to get oncall's attention to this issue.
 
 **Steps/Code to reproduce bug**

.github/ISSUE_TEMPLATE/feature_request.md

@@ -10,7 +10,7 @@ assignees: ''
 **Is your feature request related to a problem? Please describe.**
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-Tag the [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall) 
+Tag the [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall) 
 to get oncall's attention to this issue.
 
 **Describe the solution you'd like**

.github/ISSUE_TEMPLATE/question.md

@@ -9,5 +9,5 @@ assignees: ''
 ---
 
 **Your question**
-Ask a clear and concise question about Megatron-LM. Tag the [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall) 
+Ask a clear and concise question about Megatron-LM. Tag the [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall) 
 to get oncall's attention to this issue.

.github/ISSUE_TEMPLATE/regression.md

@@ -8,7 +8,7 @@ assignees: ''
 ---
 
 **Describe the regression**
-A clear and concise description of what the regression is. Tag the [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall) 
+A clear and concise description of what the regression is. Tag the [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall) 
 to get oncall's attention to this issue.
 
 **To Reproduce**

.github/pull_request_template.md

@@ -1,7 +1,7 @@
 # What does this PR do ?
 <!-- Add a one line overview of what this PR aims to accomplish. -->
 
-:warning: 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 @megatron-oncall.
+:warning: 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
 
@@ -31,7 +31,7 @@ The following process is enforced via the CODEOWNERS file for changes into `mega
 <details>
 <summary>For MRs into `main` branch</summary>
 
-Feel free to message or comment the @megatron-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!
+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!
 
 #### (Step 1): Add PR label `Expert Review`
 

.github/scripts/oncall_manager.py

@@ -23,7 +23,7 @@
 GITHUB_API_URL = "https://api.github.com"
 SCHEDULE_FILE = ".github/oncall_schedule.json"
 ROTATION_TEAM_SLUG = "mcore-oncall-rotation"
-ACTIVE_ONCALL_TEAM_SLUG = "megatron-oncall"
+ACTIVE_ONCALL_TEAM_SLUG = "mcore-oncall"
 TARGET_WEEKS = 12
 
 def get_headers():

docs/developer/contribute.md

@@ -46,11 +46,11 @@ You should receive a response within 2 business days.
 
 ### I need help, who should I ping?
 
-Use [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall).
+Use [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall).
 
 ### If my issue or PR isn't getting attention, what should I do?
 
-After 2 business days, tag the user [@megatron-oncall](https://github.com/orgs/NVIDIA/teams/megatron-oncall).
+After 2 business days, tag the user [@mcore-oncall](https://github.com/orgs/NVIDIA/teams/mcore-oncall).
 
 ### Is there a policy for issues and PRs that haven't been touched in X days? Should they be closed?