GwynBleidD

The link above is no longer working. As it is already used on the master branch in github actions workflow, the workflow is now broken.

I think it would me much better to introduce pyproject.toml support first, as it is officially documented way of specifying your dependencies. Take a look at https://www.python.org/dev/peps/pep-0621/#dependencies-optional-dependencies

Sure, I just think that this is more future-proof than `Pipfile`. Pipenv will probably at some point move to `pyproject.toml` to be compatible both with this PEP and with other...

Maybe extend the blacklist/highlight functionality to allow matching specific redeems that you don't want to see?

Commenting to make stale bot happy :)

There are 2 problems I'm encountering when I need to provide the value for the action upfront: 1. User won't see any actions from my plugin without touching the Yubikey...

Is there any summary what we will lose when moving project dependencies into the `PEP-621`/`PEP-631` specification? I know optional dependencies/extras will be defined quite different and wouldn't allow to automatically...

@henryiii is the self-referencing in pip documented somewhere? Or is it just some side-effect of how pip works internally?

I'm working on PR for that and I need some confirmation of current logic and if we want preserve some part of it. As far as my understanding goes, currently...

For now I've implemented it with assumption that: 1. local `.ykman` directory stays as is. 2. `~/.ykman` directory is not being moved to new location 3. when `~/.ykman` directory exists,...