SShortSingh.
Back to feed

Git Workflow Explained: From Working Directory to Pushing Code on GitHub

0
·1 views

Git is an open-source version control system that helps developers track file changes, record who made them, and collaborate without overwriting each other's work. The core workflow involves four stages: making changes in a working directory, staging selected files with 'git add', committing them as a snapshot with 'git commit', and pushing to a remote repository on GitHub. Staging allows developers to selectively choose which changes to include in a commit before finalizing them. Git also supports branching, which lets users work on isolated copies of a project and later merge changes back into the main branch. This workflow gives teams a reliable way to manage project history and recover from errors or accidental data loss.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Why Engineers Should Build Commercial Awareness Alongside Technical Skills

A full-stack and AI systems engineer attended 21BY72 Season 4, a major Indian startup summit, where 85 ventures pitched live to around 600 investors. The experience highlighted that technology alone is a means to a business end, and engineers who grasp commercial context make sharper architectural and product decisions. Watching founders be judged on whether they solved a paying customer's problem — not on technical cleverness — reframed how the author thinks about engineering priorities. Understanding business constraints such as cost, speed to market, and customer identity was shown to improve trade-offs rather than distract from technical work. The author argues that pairing technical depth with commercial awareness is what separates well-rounded engineers from those who hit an early career ceiling.

0
ProgrammingDEV Community ·

Developer builds Mac sleep tool that auto-recovers under battery and thermal stress

A developer has created Afterlid, a macOS utility that manages system sleep across three distinct states: normal sleep, open-lid awake, and closed-lid always-on mode. Unlike the built-in caffeinate command, Afterlid specifically handles the closed-lid scenario using a privileged helper and an undocumented macOS sleep setting. The tool automatically drops its wake assertion and restores default sleep behaviour when the battery falls below 30 percent while unplugged, thermal pressure becomes critical, or eight hours have elapsed. The developer emphasised that robust recovery logic — not just activation — is the core engineering challenge in building system utilities. Because the implementation relies on undocumented macOS internals, the developer stresses the importance of thorough hardware testing and transparent release notes.

0
ProgrammingDEV Community ·

Free API lets developers verify Polish company VAT status and bank accounts in code

A developer has released skanfirmy.pl, a free REST API that consolidates Polish business verification data from four government sources: the Ministry of Finance, the KRS court register, GUS statistics office, and the EU VIES service. The tool allows developers to check a company's VAT status, confirm bank accounts against the official government white list, and validate EU VAT numbers via simple HTTP GET requests returning JSON. A Python code example is provided, with a note that VAT status strings are returned in Polish and must be compared in their original form to avoid silent logic errors. The API also includes an MCP server with nine tools for AI agent integration, supporting JSON-RPC 2.0 over POST with no API key required. A monitoring endpoint is available that performs daily diffs and delivers HMAC-signed webhook alerts when a company's VAT status or white-list accounts change.

0
ProgrammingDEV Community ·

Engineer reflects on finishing top 12 at GDSC DevJams 2024 with voice-control project

A software engineer led team SYNTAX TERMINATOR to a top-12 finish among over 250 teams at GDSC DevJams 2024 by building a voice-controlled home system within the hackathon's time limit. The experience highlighted how tight deadlines force engineers to prioritize ruthlessly and identify the smallest viable proof of an idea. The author argues that knowing what to leave out under time pressure is a more advanced skill than knowing what to include. Integration of components was identified as a critical and often underestimated phase that can determine a team's success or failure. The engineer concludes that decisiveness, scoping discipline, and reliable delivery under pressure are skills that translate directly to professional software development.

Git Workflow Explained: From Working Directory to Pushing Code on GitHub · ShortSingh