* feat(params.toml): enable analytics and configure Umami Analytics
Enable analytics by setting `enable` to `true` in the `[analytics]` section of the `params.toml` file. Also, configure Umami Analytics by providing the `data_website_id`, `src`, and `data_domains` values.
* feat(404.html): replace hardcoded "404 page not found" text with translated version to improve localization
* feat(README.md): add README.md file with information about the Bridget theme and its features
feat(getStarted.md): add getStarted.md file with instructions on how to get started with the Bridget theme, including installation and content management instructions
* chore(hugo.toml): update theme configuration to use "bridget" theme
feat(go.mod): add "github.com/Sped0n/bridget" module as a dependency with version v0.0.0-20231104151130-eb8ddf657d31
feat(go.sum): add checksum for "github.com/Sped0n/bridget" module with version v0.0.0-20231104151130-eb8ddf657d31
* blind commit
* chore(.prettierignore): add *.yml file extension to the list of files ignored by Prettier to maintain consistent code formatting
* chore(codeql.yml): add assets/ts directory to the list of paths to be analyzed by CodeQL
* fix(codeql.yml): fix paths config
This commit adds a new file `.github/workflows/build.yml` which contains the configuration for a GitHub Actions workflow named "Build". The workflow is triggered on push events to the `main` branch and manually through the workflow_dispatch event.
The workflow consists of two jobs: "Filter" and "Build". The "Filter" job checks for changes in specific files (`package.json` and `assets/**`) and sets an output variable `any_changed` to indicate if any of the files have changed.
The "Build" job is executed if the following conditions are met:
- The workflow is triggered on the `main` branch
- The repository is not a fork
- The "Filter" job has detected changes in the specified files
The steps in the "Build" job include:
- Checking out the repository
- Setting up Hugo with version 0.114.0 and extended mode
- Setting up pnpm version 8
- Getting the pnpm store directory and caching it
- Caching the Hugo resources directory
- Installing dependencies using pnpm
- Building the project using the `pnpm run build` command
- Pushing the built artifacts if the workflow was triggered by a merged pull request
The commit adds a new step in the workflow to set up a cache for the Hugo static site generator. This cache will store the resources used by the exampleSite, improving the build time by avoiding unnecessary downloads.
The previous commit message was updated to only commit changes if there are any. This is done to avoid unnecessary commits when there are no changes in the artifacts.
This commit adds a new workflow file `.github/workflows/eslint.yml` that sets up a workflow for running ESLint and Prettier on push to the `main` branch, pull requests targeting the `main` branch, and manually triggered workflow dispatch events.
The workflow runs on `ubuntu-latest` and consists of the following steps:
1. Checkout the repository
2. Setup pnpm version 8
3. Get the pnpm store directory path
4. Setup pnpm cache using the store path
5. Install dependencies using pnpm
6. Run ESLint and Prettier linting
7. Configure git user email and name for the commit
8. Check if there are any changes using `git diff`
9. If there are changes, add all changes and commit with the message "style: ESLint && Prettier"
10. Push the changes to the repository
The change was made to include a new step in the workflow to set up Hugo with version 0.83.0 and enable extended mode. This is necessary to ensure that the correct version of Hugo is used and that extended features are available during the build process.
This commit adds a new GitHub Actions workflow file, artifacts.yml, which is triggered on push events to the main branch. The workflow consists of two jobs: "filter" and "build".
The "filter" job checks if any of the specified files (package.json and assets/**) have changed. If any file in the scope has changed, a step is executed. Otherwise, the workflow is prevented from running.
The "build" job is executed if the branch is main and the repository is not a fork. It performs the following steps:
1. Checkout the repository
2. Setup pnpm package manager
3. Get the pnpm store directory path
4. Setup pnpm cache using actions/cache
5. Install dependencies using pnpm
6. Build the artifacts
7. Configure git user email and name
8. Add all changes to the commit and commit with the message "build: update bundled artifacts [skip ci]"
9. Push the changes to the repository
