Rehab Ragab

I've encountered a limitation where every job requires a runner, even when the task does not involve compute-heavy operations. In Azure DevOps, we utilize agentless jobs (via pool: server) for lightweight orchestration tasks, approvals, and external API calls without consuming a runner. Current Limitations: - No way to define a job in GitHub Actions that runs without a runner. - All jobs, even those performing trivial tasks (like calling a webhook), must allocate a GitHub-hosted or self-hosted runner. - Cannot implement lightweight orchestration workflows without incurring unnecessary runner usage. Why This Matters: - Having agentless job support would benefit teams by: - Reducing cost and resource usage for trivial tasks. - Enabling cleaner orchestration and control flow (e.g., delays, approvals, or external service triggers). - Aligning with practices used in other systems like Azure Pipelines.

I've observed that changes to certain fields specifically built-in fields like Priority and Size, as well as custom fields such as Date Closed and Week Number are not being logged in the GitHub issue timeline or history. This makes it difficult to track important updates and introduces gaps in traceability. Current Limitations: - Changes to custom fields (like Priority, Size, Date, or text) aren’t logged anywhere. - There’s no API or webhook support to capture when fields are updated, by whom, or what the values were before/after. Why This Matters: Being able to track field updates is important for: - Transparency and accountability - Workflow automation - Compliance and reporting

The DevOps Visions Community Blog is a dedicated platform where we regularly publish blog posts contributed by our inspiring community heroes. These members share their experiences, insights, and practical knowledge across various DevOps topics—helping others learn, grow, and stay updated with real-world practices from within the community.

This session introduced GitHub Copilot Workspace—a Copilot-native, AI-powered development environment designed to help developers go from idea to implementation faster and more efficiently. Launched as a Technical Preview on April 29, Copilot Workspace allows users to generate working code from natural language prompts, significantly streamlining daily development tasks. The session demonstrated how developers can: - Turn concepts into structured projects with minimal setup - Boost productivity by reducing repetitive coding tasks - Use AI assistance to improve focus and workflow consistency Whether you're new to GitHub Copilot or looking to get more out of your development workflow, this session offered a hands-on look at how Copilot Workspace can elevate your coding experience.

My personal website, serves as a centralized hub for my technical contributions across DevOps, Azure, GitHub, and automation. I’ve published 19+ detailed blog posts designed to help developers and IT professionals solve practical challenges. It features: - In-depth blog posts on topics like Auto-Close Sub-Issues When Parent Issue Is Closed in GitHub, Deploying .NET to Azure App Service using GitHub Actions, securing Azure DevOps work items, preparing for GitHub Actions certification, and more. - Hands-on tutorials and guides that empower developers to implement CI/CD pipelines, GitHub workflows, and cloud infrastructure step-by-step - Open-source resources, including scripts, workflows, and GitHub repositories to save others time and streamline developer workflows Each post is designed to be practical, clear, and solution-focused, supporting professionals at different levels. I focus on solving real-world problems, simplifying complex topics, and encouraging continuous learning.