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

[GH-ISSUE #1075] Standardize and clean up workflow naming conventions for TinyTorch and analysis #1681

New Issue
Closed
opened 2026-04-11 08:01:59 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-11 08:01:59 -05:00
Owner
Copy Link

Originally created by @profvjreddi on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1075

Currently, our repository contains multiple workflow files that support both TinyTorch and the analysis part. The workflow names are inconsistent and may cause confusion when expanding or maintaining CI/CD operations. We should clean up and standardize the naming conventions of all workflows to:

  • Clearly distinguish between TinyTorch workflows and analysis workflows.
  • Make future maintenance and onboarding easier.
  • Avoid ambiguity for contributors and reviewers.

Tasks:

  • List all workflow files and their purposes.
  • Propose and implement a clear, consistent naming scheme for CI workflows related to TinyTorch and analysis.
  • Update documentation and workflow references if necessary.

This cleanup will help streamline development processes and reduce errors due to misidentified workflows.

Originally created by @profvjreddi on GitHub (Dec 11, 2025). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1075 Currently, our repository contains multiple workflow files that support both TinyTorch and the analysis part. The workflow names are inconsistent and may cause confusion when expanding or maintaining CI/CD operations. We should clean up and standardize the naming conventions of all workflows to: - Clearly distinguish between TinyTorch workflows and analysis workflows. - Make future maintenance and onboarding easier. - Avoid ambiguity for contributors and reviewers. **Tasks:** - List all workflow files and their purposes. - Propose and implement a clear, consistent naming scheme for CI workflows related to TinyTorch and analysis. - Update documentation and workflow references if necessary. This cleanup will help streamline development processes and reduce errors due to misidentified workflows.
GiteaMirror added the area: tinytorcharea: tools labels 2026-04-11 08:01:59 -05:00
GiteaMirror commented 2026-04-11 08:02:00 -05:00
Author
Owner
Copy Link

@oamazonasgabriel commented on GitHub (Jan 29, 2026):

Hi @profvjreddi - I'd like to work on this and share a Pull Request with the selected approach and tooling used - thanks for the opportunity!

<!-- gh-comment-id:3816458566 --> @oamazonasgabriel commented on GitHub (Jan 29, 2026): Hi @profvjreddi - I'd like to work on this and share a Pull Request with the selected approach and tooling used - thanks for the opportunity!
GiteaMirror commented 2026-04-11 08:02:01 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jan 29, 2026):

Hi @GabrielAmazonas -- any contributions are certainly welcome, but I just realized that since this issue was created, I've cleaned the code up quite a bit and fixed many bugs and issues. Nonetheless, if you spot something, feel free to let me know. This is an open-source project because the intent is for others to contribute. Thank you for volunteering!

<!-- gh-comment-id:3817310706 --> @profvjreddi commented on GitHub (Jan 29, 2026): Hi @GabrielAmazonas -- any contributions are certainly welcome, but I just realized that since this issue was created, I've cleaned the code up quite a bit and fixed many bugs and issues. Nonetheless, if you spot something, feel free to let me know. This is an open-source project because the intent is for others to contribute. Thank you for volunteering!
GiteaMirror commented 2026-04-11 08:02:01 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Apr 3, 2026):

Closing — the workflows have been significantly cleaned up since this issue was created. Thanks @GabrielAmazonas for raising it!

<!-- gh-comment-id:4184723456 --> @profvjreddi commented on GitHub (Apr 3, 2026): Closing — the workflows have been significantly cleaned up since this issue was created. Thanks @GabrielAmazonas for raising it!
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 area: tinytorch area: tools
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#1681
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?