semvec/pypi-packages huggingface dataset:
PFlowC 2.5.1
A net flow pilot in order to handle some proxy configuration automatically.
License: MIT
Requires Python: >=3.7
Keywords: proxy flow control

FlowPilot ~ PFC ~ Proxy Flow Control
========================================================

ProxyFlow Control
------------------------------

A net flow pilot in order to handle some proxy configuration automatically.

Usage ::

    ██████╗ ███████╗██╗      ██████╗ ██╗    ██╗ ██████╗
    ██╔══██╗██╔════╝██║     ██╔═══██╗██║    ██║██╔════╝
    ██████╔╝█████╗  ██║     ██║   ██║██║ █╗ ██║██║
    ██╔═══╝ ██╔══╝  ██║     ██║   ██║██║███╗██║██║
    ██║     ██║     ███████╗╚██████╔╝╚███╔███╔╝╚██████╗
    ╚═╝     ╚═╝     ╚══════╝ ╚═════╝  ╚══╝╚══╝  ╚═════╝

    Command line interface for Proxy Flow Controller with basic auto configurations.
    Version: 2.5.X                    By: BlackHaoke<Haoke98@outlook.com>
    Usage: pflow-cli [OPTIONS] COMMAND [ARGS]...

    Options:
      --help  Show this message and exit.

    Commands:
      off      Set off and clear all proxy config.
      on       Run proxy flow controller.
      server   Server as the Agent service for the local device in same LAN...
      version  Version

* Install:

    Run ``pip install PFlowC -U`` on the shell.

* start a local flow control service:

    Run ``pflow-cli server`` on the shell.


* set on the proxy setting:

    Run ``pflow-cli on`` on the shell.

* set off the proxy setting:

    Run ``pflow-cli off`` on the shell.

* Ask for Help:

    Run ``pflow-cli --help`` on the shell.
pkl-github-actions-step-generator 0.1.13
A simple CLI tool to generate a Pkl definition for a given action
License: MIT
Requires Python: >=3.11
Keywords: cli

# pkl-github-action-step-generator

A simple CLI tool to generate a Pkl definition for a given action

## Usage
The tool supports generating Pkl step definitions from two sources, remote or local.

For local, the command is as follows:

```sh
pkl-github-actions-step-generator from-local <path-to-action.yml> <full-reference-to-action> [-o --output <OUTPUT FILE>] [--pkl-github-actions-bindings] [--pkl-github-actions-bindings-version]
```

`full-reference-to-action` should be in the form you would use to reference the action in a workflow (e.g. `actions/checkout@v4`).

The `--pkl-github-actions-bindings` enables the generation of bindings to [pkl-github-actions](https://github.com/emilymclean/pkl-github-actions). The version flag allows you to specify a version (otherwise a default will be used).

If no output is provided, the file content will instead be output to stdout.

Remote has the same options, except it finds the `action.yml` in the remote repository:

```sh
pkl-github-actions-step-generator from-remote <full-reference-to-action> [-o --output <OUTPUT FILE>] [--pkl-github-actions-bindings] [--pkl-github-actions-bindings-version]
```

For example, to generate a file containing the definition for the checkout action, the command would be:
```sh
pkl-github-actions-step-generator from-remote actions/checkout@v4 -o checkout.pkl
```