Hi all! :wave: This is a bit overdue, I've been lu...
# welcome
j
Hi all! 👋 This is a bit overdue, I've been lurking for a while here, but I wanted to say hi. I'm a SWE, but am looking at using Pants for some hobby/homelab/spare-time stuff I am working on, just for myself. I have a monorepo with a wild mix of Shell, Go, Python, JS/TS, and a lot of Ansible files. I am looking at Pants because - while I feel it has a strong Python background - it's language-agnostic enough, and I'd like to manage some more "exotic" things. For instance, my Ansible setup is quite complex and I'd like to eventually build Ansible's inventory using Pants. (Also, I am using blaze in my day job - Pants seems close enough for me to like it 🙂 while also being simple enough to use as a one-human-show.) For now I've integrated some Python code, and I'm looking to Pants-ify some of my TS-based npm modules. I know TS support is experimental, and I've already hit some obstacles. For now I'm using
adhoc_tool
to connect my build chain - I've already encountered a few aspects I'm probably going to drop questions here about. (I'm assuming #C046T6T9U is a good channel for this? Please let me know if it's not.) I really, really like this community, and the overall Pants project, its vision, and its execution. I'm very enthusiastic about it and generally also open to contributing, though I am aware there's still some way for me to go until I reach a point I'd be comfortable with contributing. (Though I'm always happy to contribute in parts I'm able to - like proofreading texts, docs, etc.! I'd be more than happy to contribute some time, and get to know the project better this way.)
👋 5