semvec/pypi-packages huggingface dataset:
argocd-csq 0.2.2
CS tool to manage ArgoCD
Requires Python: >=3.10

# Argo CD CSQ

This is the new CS tool for managing Argo CD written in python.

# How to build
To install this tool, simply use the following command

```
pip install argocd-csq
```

# How to run
To run argocd-csq, you need to simply use the following command

```
argocd-csq
```

> **_NOTE:_**  It is very important to note that the first run of the tool will take sometime as it has to initialize some values and download some extra dependencies

After running the above command, you will see an output that will show you exactly how to run this tool.

The first thing that you need to do is to login via the command
```
argocd-csq login
```

This command will output an argocd authorization token that will be used when executing any argocd command.
pytest-gitlab-codequality 0.1.2.dev1
Collects warnings while testing and generates a GitLab Codequality Report.
Requires Python: >=3.12

# GitLab Codequality Report Provider for Pytest Warnings

Pytest plugin that generates a GitLab Codequality Report file from the warnings emitted when running the tests.

| Terminal | GitLab |
|----------|--------|
| ![Pytest warnings in the terminal](https://github.com/NiclasvanEyk/pytest-gitlab-codequality/blob/main/.github/images/terminal.png?raw=true) | ![Pytest warnings in the GitLab merge request widget](https://github.com/NiclasvanEyk/pytest-gitlab-codequality/blob/main/.github/images/gitlab.png?raw=true) |

If you run GitLab Premium or Ultimate, you should even see the warnings [right next to the code](https://docs.gitlab.com/ee/ci/testing/code_quality.html#merge-request-changes-view) in the diff view of merge requests.
The [official documentation](https://docs.gitlab.com/ee/ci/testing/code_quality.html) contains more information and screenshots.

## Getting Started

Install the plugin using a package manager of your choice

```shell
pip install pytest-gitlab-codequality
```

then specify the output location for the report using the `--gitlab-codequality-report` option

```shell
pytest --gitlab-codequality-report=pytest-warnings.json
```

Finally, tell GitLab about them during CI

```yaml
# .gitlab-ci.yml
pytest:
  stage: test
  image: python
  script:
    - pip install -r requirements.txt # Or however you install your dependencies
    - python -m pytest --gitlab-codequality-report=pytest-warnings.json

  # The three lines below are required in order for the warnings to show up!
  artifacts:
    reports:
      codequality: pytest-warnings.json
```

## Motivation

Some warnings are only surfaced during runtime, so static analyzers do not always catch them.
The screenshots at the top of this document contain the example of a questionably configured SQLAlchemy model.
Tests are a cheap way to surface such issues.

While you may run the tests locally and see these warnings there, you also might overlook them or don't know whether they were introduced by your changes or were already present before.
Either way, I think it makes sense to explicitly surface and track them during code review instead of burying them in the CI logs that nobody looks at when the tests pass.
And that is exactly why this plugin was created.
repo2prompt 0.1.0
Github repo -> prompt string
Requires Python: >=3.6

# repo2prompt

This is a simple package with minimal dependencies that turns a Github Repo's contents into a big prompt for long-context models.

Example Usage:

```python
from repo2prompt.extraction import extract_repo

extract_repo(github_url="https://github.com/vllm-project/vllm/tree", github_token="your_github_token")
```

Or 

```python
from repo2prompt.extraction import extract_repo

extract_repo(github_url="https://github.com/vllm-project/vllm/tree") # os.getenv("GITHUB_TOKEN") used internally
```