Standardize and clean up workflow naming conventions for TinyTorch and analysis #465

New Issue

GiteaMirror · 2026-03-22T15:41:43-05:00

GiteaMirror commented

2026-03-22 15:41:43 -05:00

Originally created by @profvjreddi on GitHub (Dec 11, 2025).

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). 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: tinytorch area: tools labels 2026-03-22 15:41:43 -05:00

GiteaMirror commented

2026-03-22 15:41:44 -05:00

@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!

@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-03-22 15:41:44 -05:00

@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!

@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 referenced this issue

2026-04-11 07:49:28 -05:00

[GH-ISSUE #465] Instructor manual #1439

GiteaMirror referenced this issue

2026-04-19 12:05:02 -05:00

[GH-ISSUE #465] Instructor manual #4059

GiteaMirror referenced this issue

2026-04-21 21:22:06 -05:00

[GH-ISSUE #465] Instructor manual #5401

Sign in to join this conversation.