Skip to content

Conversation

ugifractal
Copy link
Contributor

this PR add ignore for generated assets folder from vite build

ugifractal and others added 30 commits September 4, 2025 21:17
* Fix CHECKOV Docker security issues (brisbanesocialchess#554)

* Update Dockerfile

update the code

* Update Dockerfile

---------

Co-authored-by: John Bampton <[email protected]>
* Refactor tailwind.css: Change import statement to use URL and reorganize hover effect styles

* Refactor role styles in tailwind.css: Consolidate border and color properties for roles

* Fix import statement and clean up whitespace in tailwind.css
…ss#580)

* Remove duplicate npm-ci hook; refactor local hooks

* Update .pre-commit-config.yaml
* Natural language fixes in Markdown files

* Update DEVELOPER_HELP.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* pre-commit prettier check JS files

JS files were not being checked so there was a difference when running pre-commit and prettier manually via `npm run format`
)

* Format base.njk with Prettier and run pre-commit hooks

* Optimize PNGs via pre-commit (oxipng)

* Unchanged package-lock.json and package.json

* Removed Cdn

* Apply pre-commit autofixes (EOF newline, oxipng)

* Update frontend/_includes/layouts/base.njk

---------

Co-authored-by: John Bampton <[email protected]>
* Create .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update .deepsource.toml

* Update .deepsource.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Validate codecov.yml file with curl

* Fix up
* Test Docker with GitHub Actions

* Update .github/workflows/docker-ci.yml
Copy link
Contributor

Summary of Changes

Hello @ugifractal, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving repository cleanliness by updating the .gitignore file. The change ensures that the assets/ directory, which typically contains generated build output from tools like Vite, is excluded from version control. This prevents unnecessary files from being committed and keeps the repository focused on source code.

Highlights

  • Git Ignore Update: Added assets/ to the .gitignore file to prevent generated build assets from being tracked by Git.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

deepsource-io bot commented Sep 20, 2025

Here's the code health analysis summary for commits 4edd459..ee7f268. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗
DeepSource Secrets LogoSecrets✅ SuccessView Check ↗
DeepSource Shell LogoShell✅ SuccessView Check ↗
DeepSource Docker LogoDocker✅ Success
🎯 1 occurence resolved
View Check ↗
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to ignore generated assets from the Vite build process by adding assets/ to the .gitignore file. My review of the project's configuration files (vite.config.js and package.json) suggests that the build artifacts are actually generated in the _site/ and _deploy/ directories. Therefore, adding assets/ to .gitignore might not achieve the desired outcome. I've provided a suggestion to ignore the correct build output directories to ensure generated files are not tracked by version control.


# Build output
dist/
assets/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

While the intention to ignore generated assets is correct, the build configuration (vite.config.js) indicates that Vite's build output is placed in the _deploy/ directory. The generated assets will be inside _deploy/assets/.

Therefore, adding assets/ here will not have the intended effect for Vite's output. To ignore all build artifacts correctly, you should consider ignoring the main build output directories:

  • Eleventy's output directory: _site/
  • Vite's output directory: _deploy/

I'd suggest ignoring these directories instead to ensure all generated files are correctly excluded from version control.

_site/
_deploy/

@github-actions github-actions bot added documentation Improvements or additions to documentation ci dependencies Pull requests that update a dependency file infra frontend labels Sep 22, 2025
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​cloudflare/​vitest-pool-workers@​0.8.699910076100100
Addedvitest@​3.2.4981007997100
Addedwrangler@​4.33.2981009496100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore ci dependencies Pull requests that update a dependency file documentation Improvements or additions to documentation frontend infra root
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants