Beginner's Guide: How to Push Your First Local Project to GitHub via SSH

·1 views

A developer new to Git and GitHub documented their hands-on learning experience after finding official documentation alone insufficient to grasp key concepts. The process began with installing Git locally, configuring a user identity, and initializing a repository inside a project folder. They then generated an SSH key, linked it to their GitHub account, and verified the secure connection without needing a password. After creating a remote repository on GitHub, they linked it to the local folder and pushed their commits online using a few terminal commands. The exercise reinforced a core workflow — init, add, commit, and push — and highlighted how version control supports collaboration and code sharing.

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)

Developer Walks Through Linking Git to GitHub via SSH for First Project

A developer documented the step-by-step process of connecting a local Git installation on Windows to a GitHub account using SSH authentication. The workflow involved configuring Git with a username and email, generating an ED25519 SSH key pair, and adding the public key to GitHub's SSH settings. A local folder named 'kenya-hospital-records-analysis' was created on the desktop, initialized as a Git repository, and populated with a README file and a data folder. The project was staged, committed, and pushed to a newly created remote GitHub repository using the SSH URL. The exercise demonstrated how SSH provides a secure method for hosting local code repositories on GitHub's cloud platform.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Step-by-Step Guide: Pushing a Local Git Project to GitHub via SSH

A beginner developer at LuxdevHQ has published a walkthrough explaining how to move a local project from Git to GitHub using command-line tools. The guide uses a Kenya Road Network Analysis project as a practical example throughout the process. It covers key steps including setting up an SSH connection, creating a local directory structure, initialising a Git repository, and staging and committing files. The tutorial also explains the difference between copying and moving files, and how to create and edit a README using the nano text editor. The process concludes with linking the local repository to a remote GitHub repo and pushing the project using git push.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google Open-Sources Long Horizon: 5 Design Patterns for Stable Long-Running AI Agents

Google has open-sourced Long Horizon, an agent harness built on its Agent Development Kit (ADK) under the Apache 2.0 license, designed to keep AI agents running reliably over days or weeks. The project was released after Google's own team ran the system internally for several weeks, uncovering recurring silent failures where agents continued operating without throwing errors despite underlying problems. Key issues discovered included broken prefix caching due to volatile prompt headers, unnecessary memory retrieval slowing every turn, and sub-agents timing out while parent agents falsely reported task completion. To address these, the team documented five design patterns covering prompt structure optimization, write-behind memory caching, robust sub-agent error handling, stateful session recovery, and tightened security guardrails. Google describes Long Horizon as a reference implementation meant to be read and adapted rather than deployed out of the box.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Android Car Head Units Hit by Silent Malware via Legitimate Update Channel

Kaspersky researchers have identified a supply chain attack targeting DoFun Android car head units, in which malware is silently installed through the device's legitimate software update system, TWCore. Attackers inject commands via an MQTT broker to download a malicious APK called JarService into the device's cache without any user interaction. Once installed, JarService executes a multi-stage payload that ultimately loads the zhima reverse proxy module, turning the head unit into a relay node for external traffic and ad click fraud. The malware reports device details to a command-and-control server every 90 minutes and awaits further instructions, while showing no visible interface on the car display. Kaspersky found no evidence of interference with driving functions, but noted that such devices typically fall outside enterprise security monitoring tools, making detection difficult.

0 comments Read more at DEV Community