chore: import upstream snapshot with attribution

2026-07-13 13:35:51 +08:00
commit c36a561cd8
2172 changed files with 455595 additions and 0 deletions
@@ -0,0 +1,24 @@
+---
+name: "\U0001F528Work Item (DEV ONLY)"
+about: Work item issue for tracking progress. Dev team only.
+title: ''
+labels: Work Item
+assignees: ''
+
+---
+
+## 🔨Work Item
+
+**IMPORTANT:**
+* This template is only for dev team to track project progress. For feature request or bug report, please use the corresponding issue templates.
+* DO NOT create a new work item if the purpose is to fix an existing issue or feature request. We will directly use the issue in the project tracker.
+
+Project tracker: https://github.com/orgs/dmlc/projects/2
+
+## Description
+
+<!-- short description of the work item -->
+
+## Depending work items or issues
+
+<!-- what must be done before this -->
@@ -0,0 +1,42 @@
+---
+name: "\U0001F41B Bug Report"
+about: Submit a bug report to help us improve DGL
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## 🐛 Bug
+
+<!-- A clear and concise description of what the bug is. -->
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1.
+1.
+1.
+
+<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
+
+## Expected behavior
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+## Environment
+
+ - DGL Version (e.g., 1.0):
+ - Backend Library & Version (e.g., PyTorch 0.4.1, MXNet/Gluon 1.3):
+ - OS (e.g., Linux):
+ - How you installed DGL (`conda`, `pip`, source):
+ - Build command you used (if compiling from source):
+ - Python version:
+ - CUDA/cuDNN version (if applicable):
+ - GPU models and configuration (e.g. V100):
+ - Any other relevant information:
+
+## Additional context
+
+<!-- Add any other context about the problem here. -->
@@ -0,0 +1,13 @@
+---
+name: "\U0001F4DA Documentation"
+about: Report an issue related to docs.dgl.ai
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## 📚 Documentation
+
+<!-- Please specify whether it's tutorial part or API reference part-->
+<!-- Describe the issue.-->
@@ -0,0 +1,29 @@
+---
+name: "\U0001F680Feature Request"
+about: Submit a proposal/request for a new DGL feature
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## 🚀 Feature
+<!-- A brief description of the feature proposal -->
+
+## Motivation
+
+<!-- Please outline the motivation for the proposal. Is your feature request
+related to a problem? e.g., I'm always frustrated when [...]. If this is
+related to another GitHub issue, please link here too -->
+
+## Alternatives
+
+<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->
+
+## Pitch
+
+<!-- A clear and concise description of what you want to happen. -->
+
+## Additional context
+
+<!-- Add any other context or screenshots about the feature request here. -->
@@ -0,0 +1,15 @@
+---
+name: "❓Questions/Help/Support"
+about: Do you need support? We have resources.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## ❓ Questions and Help
+
+Before proceeding, please note that we recommend
+using our discussion forum (https://discuss.dgl.ai) for
+general questions. As a result, this issue will
+likely be CLOSED shortly.
@@ -0,0 +1,20 @@
+## Description
+<!-- Brief description. Refer to the related issues if existed.
+It'll be great if relevant reviewers can be assigned as well.-->
+
+## Checklist
+Please feel free to remove inapplicable items for your PR.
+- [ ] The PR title starts with [$CATEGORY] (such as [NN], [Model], [Doc], [Feature]])
+- [ ] I've leverage the [tools](https://docs.google.com/document/d/1iHyj7zlmygKSk5gBPsqIqL5ASPzJSPREaNT_QdsiYA4/edit) to beautify the python and c++ code.
+- [ ] The PR is complete and small, read the [Google eng practice (CL equals to PR)](https://google.github.io/eng-practices/review/developer/small-cls.html) to understand more about small PR. In DGL, we consider PRs with less than 200 lines of core code change are small (example, test and documentation could be exempted).
+- [ ] All changes have test coverage
+- [ ] Code is well-documented
+- [ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change
+- [ ] Related issue is referred in this PR
+- [ ] If the PR is for a new model/paper, I've updated the example index [here](../examples/README.md).
+
+## Changes
+<!-- You could use following template
+- [ ] Feature1, tests, (and when applicable, API doc)
+- [ ] Feature2, tests, (and when applicable, API doc)
+-->
@@ -0,0 +1,54 @@
+name: Lint
+
+on: [pull_request]
+
+jobs:
+  lintrunner:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Pull DGL
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Checkout master and HEAD
+        run: |
+          git checkout -t origin/master
+          git checkout ${{ github.event.pull_request.head.sha }}
+
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.8'
+
+      - name: Install requirements
+        run: |
+          python -m pip install --upgrade pip
+          pip install lintrunner --user
+
+      - name: Initialize lint dependencies
+        run: lintrunner init
+
+      - name: Run lintrunner on all changed files
+        run: |
+          set +e
+          if ! lintrunner --force-color -m master --tee-json=lint.json; then
+              echo ""
+              echo -e "\e[1m\e[36mYou can reproduce these results locally by using \`lintrunner\`.\e[0m"
+              echo -e "\e[1m\e[36mSee https://github.com/pytorch/pytorch/wiki/lintrunner for setup instructions.\e[0m"
+              exit 1
+          fi
+
+      - name: Store annotations
+        if: always() && github.event_name == 'pull_request'
+        # Don't show this as an error; the above step will have already failed.
+        continue-on-error: true
+        run: |
+          # Use jq to massage the JSON lint output into GitHub Actions workflow commands.
+          jq --raw-output \
+            '"::\(if .severity == "advice" or .severity == "disabled" then "warning" else .severity end) file=\(.path),line=\(.line),col=\(.char),title=\(.code) \(.name)::" + (.description | gsub("\\n"; "%0A"))' \
+            lint.json
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }}-${{ github.event_name == 'workflow_dispatch' }}
+  cancel-in-progress: true
@@ -0,0 +1,32 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+  - cron: '0 1 * * *'
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v4.1.0
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        days-before-issue-stale: 30
+        days-before-issue-close: -1 # disable issue close
+        days-before-pr-stale: -1 # disable stale bot on pr
+        days-before-pr-close: -1 # disable stale bot on pr
+        stale-issue-message: 'This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you'
+        close-issue-message: 'This issue is closed due to lack of activity. Feel free to reopen it if you still have questions.'
+        stale-issue-label: 'stale-issue'
+        exempt-issue-labels: 'bug:confirmed,feature request,help wanted,Work Item'
+        exempt-all-issue-milestones: true