8000 Create tech stack docs (techstack.yml and techstack.md) by stack-file[bot] · Pull Request #3 · tuhinmallick/gigagan-pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Create tech stack docs (techstack.yml and techstack.md) #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Create tech stack docs (techstack.yml and techstack.md) #3

wants to merge 4 commits into from

Conversation

stack-file[bot]
Copy link
@stack-file stack-file bot commented Feb 19, 2024

Adding tech stack documentation to allow anyone to easily see what is being used in this repo without digging through config files. Two files are being added: techstack.yml and techstack.md. techstack.yml contains data on all the technologies being used in this repo. techstack.md is a visualization of the YML file and displays the tech stack data in a pretty Markdown file.

💡 Protip: techstack.md contains a comment at the top of the file that the following README snippet (with and without the logos) at the top of the file as a comment:

<--- Readme.md Snippet without images Start --->

Tech Stack

tuhinmallick/gigagan-pytorch is built on the following main stack:

Full tech stack here

<--- Readme.md Snippet without images End --->

Get the code:

## Tech Stack
tuhinmallick/gigagan-pytorch is built on the following main stack:

- [Python](https://www.python.org) – Languages
- [GitHub Actions](https://github.com/features/actions) – Continuous Integration
- [Kornia](https://kornia.github.io/) – Image Processing and Management
- [Pillow](https://python-pillow.github.io/) – Image Processing and Management

Full tech stack [here](/techstack.md)

<--- Readme.md Snippet with images Start --->

Tech Stack

tuhinmallick/gigagan-pytorch is built on the following main stack:

Full tech stack here

<--- Readme.md Snippet with images End --->

Get the code:

## Tech Stack
tuhinmallick/gigagan-pytorch is built on the following main stack:

- <img width='25' height='25' src='https://img.stackshare.io/service/993/pUBY5pVj.png' alt='Python'/> [Python](https://www.python.org) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/11563/actions.png' alt='GitHub Actions'/> [GitHub Actions](https://github.com/features/actions) – Continuous Integration
- <img width='25' height='25' src='https://img.stackshare.io/service/33820/default_8eec0fbd2eb1f7131b5c3a61d2b271c49524eb71.jpg' alt='Kornia'/> [Kornia](https://kornia.github.io/) – Image Processing and Management
- <img width='25' height='25' src='https://img.stackshare.io/service/2375/default_1f67b0ca7416a9f52beb655f90b5602d5ef74b75.jpg' alt='Pillow'/> [Pillow](https://python-pillow.github.io/) – Image Processing and Management

Full tech stack [here](/techstack.md)

@codara-ai-code-review Codara AI Code Review
Copy link

Potential issues, bugs, or flaws:

  1. /techstack.md

    • The formatting of the "Tech Stack File" section and the subsequent content with tables and images deviates significantly from the initial structure and formatting of the "Tech Stack" section. It's important to maintain consistency in formatting to ensure a cohesive and professional appearance.

  2. /techstack.yml

    • In the "techstack.yml" file, the "last_updated_on" fields are represented as datetime with timezone ("Z" signifies UTC). While this format is unambiguous, it's essential to ensure that it aligns with the expected usage and compatibility with any systems or processes that rely on this data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
size/L
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@stacksharebot
0