Metadata-Version: 2.4
Name: amsc
Version: 0.0.1
Summary: American Science Cloud
Project-URL: Homepage, https://saforem2.github.io/amsc/
Project-URL: Repository, https://github.com/saforem2/amsc
Project-URL: Documentation, https://saforem2.github.io/amsc/
Author-email: Sam Foreman <saforem2@gmail.com>
Keywords: python
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Requires-Python: <4.0,>=3.10
Description-Content-Type: text/markdown

# amsc

[![Release](https://img.shields.io/github/v/release/saforem2/amsc)](https://img.shields.io/github/v/release/saforem2/amsc)
[![Build status](https://img.shields.io/github/actions/workflow/status/saforem2/amsc/main.yml?branch=main)](https://github.com/saforem2/amsc/actions/workflows/main.yml?query=branch%3Amain)
[![codecov](https://codecov.io/gh/saforem2/amsc/branch/main/graph/badge.svg)](https://codecov.io/gh/saforem2/amsc)
[![Commit activity](https://img.shields.io/github/commit-activity/m/saforem2/amsc)](https://img.shields.io/github/commit-activity/m/saforem2/amsc)
[![License](https://img.shields.io/github/license/saforem2/amsc)](https://img.shields.io/github/license/saforem2/amsc)

American Science Cloud

- **Github repository**: <https://github.com/saforem2/amsc/>
- **Documentation** <https://saforem2.github.io/amsc/>

## 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:saforem2/amsc.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

- Create an API Token on [PyPI](https://pypi.org/).
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting [this page](https://github.com/saforem2/amsc/settings/secrets/actions/new).
- Create a [new release](https://github.com/saforem2/amsc/releases/new) on Github.
- Create a new tag in the form `*.*.*`.

For more details, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/cicd/#how-to-trigger-a-release).

---

Repository initiated with [fpgmaas/cookiecutter-uv](https://github.com/fpgmaas/cookiecutter-uv).
