https://github.com/straymat/explore-bqss
https://github.com/straymat/explore-bqss
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/straymat/explore-bqss
- Owner: strayMat
- License: mit
- Created: 2025-02-27T15:38:40.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-08-25T17:53:50.000Z (10 months ago)
- Last Synced: 2025-10-06T17:02:46.478Z (9 months ago)
- Language: HTML
- Size: 400 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# explore-bqss
[](https://img.shields.io/github/v/release/strayMat/explore-bqss)
[](https://github.com/strayMat/explore-bqss/actions/workflows/main.yml?query=branch%3Amain)
[](https://codecov.io/gh/strayMat/explore-bqss)
[](https://img.shields.io/github/commit-activity/m/strayMat/explore-bqss)
[](https://img.shields.io/github/license/strayMat/explore-bqss)
Testing d'uv pour une analyse de données.
- **Github repository**:
- **Documentation**
## Getting started with your project
### 1. Create a New Repository
First, create a repository on GitHub with the same name as this project, and then run the following commands:
```bash
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:strayMat/explore-bqss.git
git push -u origin main
```
### 2. Set Up Your Development Environment
Then, install the environment and the pre-commit hooks with
```bash
make install
```
This will also generate your `uv.lock` file
### 3. Run the pre-commit hooks
Initially, the CI/CD pipeline might be failing due to formatting issues. To resolve those run:
```bash
uv run pre-commit run -a
```
### 4. Commit the changes
Lastly, commit the changes made by the two steps above to your repository.
```bash
git add .
git commit -m 'Fix formatting issues'
git push origin main
```
You are now ready to start development on your project!
The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.
To finalize the set-up for publishing to PyPI, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/codecov/).
## Releasing a new version
---
Repository initiated with [fpgmaas/cookiecutter-uv](https://github.com/fpgmaas/cookiecutter-uv).