Wow, Config.tips seems like an absolute gem for developers! I appreciate the value of a platform dedicated to sharing config tips and tricks, especially when navigating the YAML, CircleCI, Nginx, Git, and package.json landscape.
I've been in situations where config files have caused me severe headaches, so I'm curious to know how Config.tips ensures the quality and accuracy of the tips shared on the platform. Are there any measures in place to prevent incorrect or outdated information from being shared?
Additionally, I love that Config.tips encourages contributions to open source. It would be great to learn more about how developers can get involved and contribute their own config tips. Are there any specific guidelines or processes in place for submitting tips?
Lastly, I'm wondering if there are plans to expand the range of available tips beyond YAML, CircleCI, Nginx, Git, and package.json. Are there any other config areas that you are considering adding in the future? It would be interesting to explore tips for other popular technologies as well.
Overall, I'm impressed with what Config.tips offers, and I can't wait to dive in and explore the treasure trove of tips and tricks. Keep up the fantastic work! 💪🚀
hey @alexandre_savigny1 ! Nice collection of configs. Have you considered adding configs for NestJS and Github actions? Giving their increasing popularity I believe it would be really helpful for the dev community.