Challenge 1: Setup of Enhanced Development Codespace

[antonio-bravo]

Challenge 1: Setup of Enhanced Development Codespace

As a Product Owner, I want to establish a cutting-edge development environment in a codespace that comes pre-equipped with essential extensions and robust debugging capabilities, so that the five teams from WBFH who are onboarding can get up to speed with our codebase as efficiently as possible. We aim to make their first commit within an hour.

Why:

• Rapid Onboarding: Five teams from WBFH are integrating into our project. A streamlined, ready-to-go development environment will minimize setup time and remove barriers to initial contributions.
• Efficiency in Development: By reducing the initial setup time to under an hour, we empower new team members to start contributing to the project immediately, boosting overall productivity and collaboration.
• Consistency Across Setups: Ensuring every new codespace uses the pre-configured template will maintain consistency and reliability across all development setups.

Acceptance Criteria:

1. Codespace Configuration:

   • The codespace must be set up to support C# development.
   • Essential extensions need to be pre-installed:
     • Csharp
     • REST Client
     • CSharp DevKit
     • GitHub Actions
   • Add the following essential features:
     • Azure CLI
     • Dotnet CLI
     • GitHub CLI
     • PowerShell
     • Node.js
   • The configuration for this codespace must be committed to the repository to ensure every new codespace is created with this predefined setup.

2. Debugging Enabled:

   • Debugging must be enabled within the codespace to allow setting and hitting breakpoints.
   • Ensure the code runs reliably and effectively.

3. Port Forwarding for Application Testing:

   • The codespace must allow the application to run with port forwarding, enabling testing directly from the browser.
   • This enables quick feedback loops and faster iterations in development.

Tasks:

• [ ] Setup a base codespace environment capable of running C#.
• [ ] Install the specified extensions and features to enhance development capabilities.
• [ ] Configure the codespace to enable debugging with support for breakpoints.
• [ ] Ensure port forwarding is enabled and tested to allow in-browser application runs.
• [ ] Commit the codespace configuration to the main repository to standardize the development environment across new codespaces.
• [ ] Create a new codespace based on the created configuration and keep it running.

---

"Setting standards is not an innovation, but adhering to them is an art." - Simon Sinek

[antonio-bravo]

Folks! I got this amazing idea. I wanted to share it with you, but somehow the Wiki in your repo has not been enabled. I cannot do it right now. I am on the road and use the mobile app! So.. Can you please navigate to the wiki page and make sure you enabled it? You see a button Create First Page. Click it, and then press Save Page You can find some more instructions on how to do that here! https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

I will keep an 👁️ eye on the Wiki. The moment when you have created the page, I will post my thoughts!

[antonio-bravo]

Folks! I got this amazing idea. I wanted to share it with you, but somehow the Wiki in your repo has not been enabled. I cannot do it right now. I am on the road and use the mobile app! So.. Can you please navigate to the wiki page and make sure you enabled it? You see a button Create First Page. Click it, and then press Save Page You can find some more instructions on how to do that here! https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

I will keep an 👁️ eye on the Wiki. The moment when you have created the page, I will post my thoughts!

Hey team, just had a "Eureka!" moment on how to nail this issue 🌟. It harkens back to something I tackled during my last hackathon where we streamlined Docker containers for dev environments. Super similar vibes! 🚀

I’ve spun up a Wiki that outlines some thoughts based on that experience. We'll utilize a containerized approach called GitHub Codespaces! This can ensure that all the necessary extensions and settings are baked right into a container image that everybody can use! Awesome 🌈! This method will not only speed up the onboarding but also lock down consistency across any new IDE fired up by our team members. And... best of all, time to first commit will plunge! 🏊‍♂️

• Check out the Wiki page for detailed steps and configuration tips.
• Need to dive deeper into this setup or get hands-on guidance? Just hit /help 🛠️.
• Want a detailed, step-by-step guide to really master this setup? Type /expert-tip for a comprehensive breakdown 📚.
• If you'd like me to check that your setup aligns perfectly with our standards, just type /verify and I'll take a look! 🔍.
• Ready for Emily to take the lead on configuring and committing this to our repo? Type /fix 👷🏽.

Oh! And don't forget, if you want to move on to a new challenge, you need to type /finish. Emily will close the issue for you, so do not close it yourself. But...first use /fix and use the code provided to be fully prepped for the next challenge

[antonio-bravo]

/expert-tip I've managed to free up some time 🕙 🌃. I added this Step by Step Wiki page for you! Hope this helps!

/fix

I am on it! I asked the offshore team to get this ready. It will cost some money, but they created the code. Alex will create a PR that you can merge. Stay tuned!

✅ WHOOOP! Already got the code! PR is here, ready to merge! https://github.com/globaldevopsexperience/gdex-emergency/pull/3

/finish

🤩 You did it !! Robert is going to be thrilled! I will directly update our corporate communication team to put this on the intranet! Well done! I'll close this issue for now! Just navigate to the Globoticket Intranet to continue!