My First Github Project: From a Local Folder to Github Using Git and SSH

After much deliberation, Monday, August 10th, 2026 was the day I officially entered the realm of data and embarked on my journey with GitHub. In this piece, I will recount my first week as a GitHub user, detailing the steps taken to set up and utilize the platform.

Upon the outset of the week, we were introduced to a variety of tools including Dev.to, Markdown, Git, GitHub, Dbeaver, Visual Studio Code, Windows PowerShell, Zoho Cliq, PostgreSQL, and Iven. The instructor emphasized that the initial focus would be on tool installations rather than active learning, easing the initial apprehensions of attendees who were new to the learning environment.

Dev.to, a platform for writing articles, was the first to be installed. Users set up an account using their Google credentials. A standout feature of Dev.to is its ability to syndicate your written content to your profile, creating a community of developers with diverse interests. Over time, Dev.to has evolved into a platform that offers job opportunities through technical writing.

Navigating Dev.to was straightforward due to its user interface, which combined elements of both social networks and article platforms. DEV Challenges often took place in the form of mini Hackathons, providing a fun way to build experience and showcase learned skills to the community and potential employers. Reading Lists allowed users to curate a list of articles for easy reference.

DEV++ was an incentive program rewarding participants in DEV challenges. The DEV Education Tracks offered learning programs that combined theoretical knowledge and hands-on experience.

Markdown, a simple markup language, was introduced on day one. It enabled text formatting and switched between an Edit page for writing and a Preview page for displaying the output. Key formatting rules included concise paragraph length, clear titles, headings denoted by #, ##, and ###, and the use of backticks for inline code and triple backticks for code blocks.

Day two commenced with the installation of PostgreSQL, a database management system. Dbeaver, an application for easier database interaction, was used to connect to various databases including PostgreSQL, MySQL, Oracle, among others. Aiven, a cloud data platform, was utilized for creating and managing services, including PostgreSQL & MySQL, for our onboarding session.

GitHub was introduced as a cloud-based developer platform for storing, managing, and sharing software code. It was stressed that a professional GitHub account would serve as a resume, even when seeking opportunities. Git, a control software system, was explained as a tool for managing versions of source code or data. GitHub showcased projects on a cloud-based environment, while Git handled the local version.

Common Git commands included COMMIT, PUSH, PULL, and CLONE. COMMIT saved a checkpoint in the project's history, PUSH sent data to a server, PULL retrieved data from a source, and CLONE downloaded an existing repository to the local computer. To check if a tool was installed, the git --version command was used in Git Bash. If the result was a defined version, the tool was installed; otherwise, it was not.

Lastly, configuring your identity with Git required providing your name and email address that matched the one used for your GitHub account.