github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-21 13:31:55 -05:00
Code Issues 114 Packages Projects Releases 24 Wiki Activity

[PR #1172] [MERGED] fixed google auth allow iframe, slow index.html #8017

New Issue
Closed
opened 2026-04-27 17:18:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-27 17:18:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/1172
Author: @kai4avaya
Created: 2/13/2026
Status: ✅ Merged
Merged: 2/14/2026
Merged by: @profvjreddi

Base: dev ← Head: fix-google-login-iframe

📝 Commits (1)

  • ed39f89 fixed google auth allow iframe, slow index.html

📊 Changes

1 file changed (+6 additions, -5 deletions)

View changed files

📝 tinytorch/site/extra/community/index.html (+6 -5)

📄 Description

Hi Vijay,
I actually pushed most of this to dev last week. But I noticed that the updates to the community site did not get propagated to the live site. I'm thinking - do you need to do a rebuild to render the newest updates?

Kai

🔄 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/1172 **Author:** [@kai4avaya](https://github.com/kai4avaya) **Created:** 2/13/2026 **Status:** ✅ Merged **Merged:** 2/14/2026 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `dev` ← **Head:** `fix-google-login-iframe` --- ### 📝 Commits (1) - [`ed39f89`](https://github.com/harvard-edge/cs249r_book/commit/ed39f89d5af09523034c3e0a35ea79cb2047e3dd) fixed google auth allow iframe, slow index.html ### 📊 Changes **1 file changed** (+6 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `tinytorch/site/extra/community/index.html` (+6 -5) </details> ### 📄 Description Hi Vijay, I actually pushed most of this to dev last week. But I noticed that the updates to the community site did not get propagated to the live site. I'm thinking - do you need to do a rebuild to render the newest updates? Kai --- <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-27 17:18:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
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#8017
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?