🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко)

@abhinavsingh alright. What's your release flow? _Right now_, having https://github.com/abhinavsingh/proxy.py/pull/682 merged, you can download artifacts (wrapped as one archive with GHA) from the workflow run, unpack them and publish with...

Re:codecov — AFAIK the action only uploads the reports but their backend reads the config separately from that via the GitHub App you have installed. I don't see the connection...

re:pylint — it is totally expected that it consumes more resources. By nature, it also has checks evaluating the code by dynamically importing it. This is why it's capable of...

> At some point we may even have to abstract out linter steps, so that they can run when a matching file changes. It should be possible to achieve with...

> Lately I am getting a lot of these coverage errors locally. Behavior is also kind of weird. This may be happening if you run some tests in parallel and...

> But won't we have to carry forward that clause into tox cli flags? I usually have a separate job to set multiple flags to prevent copy-paste and improve consistency...

re:releases — now that the testing of the published thing is satisfied, I'll send a PR integrating setuptools-scm. The following PR will add a `workflow_dispatch` trigger allowing to type in...

> I am wondering if this is still necessary? My _ideal_ preference is to have a single > release PR merging into master branch. But if there are certain restrictions...

I just noticed that there are no Git tags in the repo. How do you find the versions corresponding to the published dists? This is quite surprising. Could you at...

Here's the versioning bit: * https://github.com/abhinavsingh/proxy.py/pull/715 It is based on tags so you should tag the previous version for this to properly calculate the value. And the GHA bit: *...