github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-06 17:49:07 -05:00
Code Issues 85 Packages Projects Releases 24 Wiki Activity

[PR #201] [CLOSED] Yanjing updates #2576

New Issue
Closed
opened 2026-04-13 13:10:52 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 13:10:52 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/201
Author: @profvjreddi
Created: 5/17/2024
Status: ❌ Closed

Base: main ← Head: yanjing-updates

📝 Commits (9)

  • 9a61428 add actions for file transfer
  • 62d0a4f update actions with develop branch
  • e1f2ca4 Update readme and contributors.qmd with contributors
  • 64a49f2 address merge conflict
  • 435882e develop -> dev
  • 4420ad2 Update readme and contributors.qmd with contributors
  • 076aafa change file name
  • eb7aa0d Merge branch 'dev' of github.com:harvard-edge/cs249r_book into dev
  • 4229807 Update readme and contributors.qmd with contributors

📊 Changes

7 files changed (+53 additions, -19 deletions)

View changed files

📝 .all-contributorsrc (+6 -6)
📝 .github/workflows/auto-add-contributors.yml (+1 -0)
📝 .github/workflows/build_pages.yml (+1 -0)
➕ .github/workflows/build_pages_dev.yml (+31 -0)
📝 .github/workflows/build_pages_windows.yml (+2 -1)
📝 README.md (+6 -6)
📝 contents/contributors.qmd (+6 -6)

📄 Description

Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist.

  1. Content

    • The chapter content is complete and covers the topic in detail.
    • All technical terms are well-defined and explained.
    • Any code snippets or algorithms are well-documented and tested.
    • The chapter follows a logical flow and structure.

  2. References & Citations

    • All references are correctly listed at the end of the chapter.
    • In-text citations are used appropriately and match the references.
    • All figures, tables, and images have proper sources and are cited correctly.

  3. Quarto Website Rendering

    • The chapter has been locally built and tested using Quarto.
    • All images, figures, and tables render properly without any glitches.
    • All images have a source or they are properly linked to external sites.
    • Any interactive elements or widgets work as intended.
    • The chapter's formatting is consistent with the rest of the book.

  4. Grammar & Style

    • The chapter has been proofread for grammar and spelling errors.
    • The writing style is consistent with the rest of the book.
    • Any jargon is clearly explained or avoided where possible.

  5. Collaboration

    • All group members have reviewed and approved the chapter.
    • Any feedback from previous reviews or discussions has been addressed.

  6. Miscellaneous

    • All external links (if any) are working and lead to the intended destinations.
    • If datasets or external resources are used, they are properly credited and linked.
    • Any necessary permissions for reused content have been obtained.

  7. Final Steps

    • The chapter is pushed to the correct branch on the repository.
    • The Pull Request is made with a clear title and description.
    • The Pull Request includes any necessary labels or tags.
    • The Pull Request mentions any stakeholders or reviewers who should take a look.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/201 **Author:** [@profvjreddi](https://github.com/profvjreddi) **Created:** 5/17/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `yanjing-updates` --- ### 📝 Commits (9) - [`9a61428`](https://github.com/harvard-edge/cs249r_book/commit/9a614282501a2cca9f526d29d07cd5eadc9b877e) add actions for file transfer - [`62d0a4f`](https://github.com/harvard-edge/cs249r_book/commit/62d0a4fd58d583d5efc7e633f17d5abd60b07782) update actions with develop branch - [`e1f2ca4`](https://github.com/harvard-edge/cs249r_book/commit/e1f2ca490d58e388dba1a8262c278998d1160ecd) Update readme and contributors.qmd with contributors - [`64a49f2`](https://github.com/harvard-edge/cs249r_book/commit/64a49f272754f7d5fc4b85b2d6d7af2a6bff846c) address merge conflict - [`435882e`](https://github.com/harvard-edge/cs249r_book/commit/435882e45f13d0e637f9335b5104e7c34dc999bc) develop -> dev - [`4420ad2`](https://github.com/harvard-edge/cs249r_book/commit/4420ad2019924cbe1dbe46f6fe090cdb596fa0a2) Update readme and contributors.qmd with contributors - [`076aafa`](https://github.com/harvard-edge/cs249r_book/commit/076aafafdc393a99f3b0653a78908fe5ac74404f) change file name - [`eb7aa0d`](https://github.com/harvard-edge/cs249r_book/commit/eb7aa0d4453ce8d5d4b648d209f6e2926bbedbf8) Merge branch 'dev' of github.com:harvard-edge/cs249r_book into dev - [`4229807`](https://github.com/harvard-edge/cs249r_book/commit/422980789fa4d0a0779661ea76e37d350ee439b3) Update readme and contributors.qmd with contributors ### 📊 Changes **7 files changed** (+53 additions, -19 deletions) <details> <summary>View changed files</summary> 📝 `.all-contributorsrc` (+6 -6) 📝 `.github/workflows/auto-add-contributors.yml` (+1 -0) 📝 `.github/workflows/build_pages.yml` (+1 -0) ➕ `.github/workflows/build_pages_dev.yml` (+31 -0) 📝 `.github/workflows/build_pages_windows.yml` (+2 -1) 📝 `README.md` (+6 -6) 📝 `contents/contributors.qmd` (+6 -6) </details> ### 📄 Description Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist. 1. **Content** - [ ] The chapter content is complete and covers the topic in detail. - [ ] All technical terms are well-defined and explained. - [ ] Any code snippets or algorithms are well-documented and tested. - [ ] The chapter follows a logical flow and structure. 2. **References & Citations** - [ ] All references are correctly listed at the end of the chapter. - [ ] In-text citations are used appropriately and match the references. - [ ] All figures, tables, and images have proper sources and are cited correctly. 3. **Quarto Website Rendering** - [ ] The chapter has been locally built and tested using Quarto. - [ ] All images, figures, and tables render properly without any glitches. - [ ] All images have a source or they are properly linked to external sites. - [ ] Any interactive elements or widgets work as intended. - [ ] The chapter's formatting is consistent with the rest of the book. 4. **Grammar & Style** - [ ] The chapter has been proofread for grammar and spelling errors. - [ ] The writing style is consistent with the rest of the book. - [ ] Any jargon is clearly explained or avoided where possible. 5. **Collaboration** - [ ] All group members have reviewed and approved the chapter. - [ ] Any feedback from previous reviews or discussions has been addressed. 6. **Miscellaneous** - [ ] All external links (if any) are working and lead to the intended destinations. - [ ] If datasets or external resources are used, they are properly credited and linked. - [ ] Any necessary permissions for reused content have been obtained. 7. **Final Steps** - [ ] The chapter is pushed to the correct branch on the repository. - [ ] The Pull Request is made with a clear title and description. - [ ] The Pull Request includes any necessary labels or tags. - [ ] The Pull Request mentions any stakeholders or reviewers who should take a look. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 13:10:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#2576
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?