simonecorsi / github-languages-colors

🎨 This npm package exposes github language colors codes in js, json and css and updates daily from github definitions!

Hi there, I am Simone!

Just a sunny Italian guy with a deep passion for technology, skateboarding, punk music, and photography. I consider myself a language-agnostic and battle-tested engineer, with a particular focus on the whole web stack, especially backends.

• Tech Leader: at Immobiliare.it, Italy's #1 Real Estate Portal. Within the Developer Experience and Technological Advancement team, I contribute as a Senior Software Engineer and Solution Architect. I take pride in collaborating with my team to develop robust B2B/B2C solutions, including APIs, databases, and system integrations.

• Open Source Advocate: In addition to my responsibilities at Immobiliare.it, I am also one of the founding members of the internal open source committee. By actively fostering collaboration and knowledge sharing, I strive to create a culture of innovation and continuous improvement within the organization.

• Consulting Background: With a long experience in consulting, I bring a diverse range of knowledge and expertise to my work. Throughout my career, I have had the privilege of leading and contributing to the development of complete solutions for various businesses. This includes frontend and backend development, API design, database management, and system integrations. I have been fortunate to work across industries such as retail, oil, sports, banking, and events.

---

🧰 Toolbox

---

---

📚 Feed

---

You can find a curated list of all the projects I've starred over the last decade on GitHub at simonecorsi/awesome. It's presented in an easy-to-read format, allowing you to explore my interests and the projects I find valuable.

Would you like to have your own personalized feed? Give my Github Action a try! It generates a feed based on your starred projects, providing a convenient way to showcase your preferences and engage with the community

github-languages-colors's Issues

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀