Alex Chantavy
Alex Chantavy
Hey @abhinav-1305, please fix the linter errors and ensure proper testing is done for this module by following the PR checklist. It's not ready for a review until that is...
Hi @Saru2003 have you tested this? Please resolve the linter errors so we can review, thank you!
Hey good to meet you, with open source the best way to get involved isn't to ask for permission, it's to look around and get involved where you feel strongly...
@blah-bleh-hmm - Only if you find them interesting. Working on issues is a great way to get feel for what it's like to work us and show that you understand...
I'm not a user of the Azure module (yet) so a major version upgrade makes me a bit nervous
@krishi-agrawal - no need to ask for permission, just do it haha. The one tricky part is we need to represent the root user of the account as its own...
Oh oh maybe we could do this in pre-commit to catch it before CI also ``` repos: - repo: https://github.com/astral-sh/uv-pre-commit # uv version. rev: 0.9.13 hooks: - id: uv-lock ```...
I played around with this earlier with the pre-commit hooks and it blocked one of my commits when I thought my uv.lock was up to date. I'm a bit confused...
Hi @pvasilevich, thanks for filing this. There are a few options for addressing this: 1. **Decompose the large graphql query**. We use the GitHub graphql API because it tends to...