Skip to main content

upload a existing project from system to github

How to upload a existing project from system to github?

Here, I will show a live example to upload a existing project from your machine to github.

First of all I want you to understand that you should or can't upload your existing project directly to git hub website using github UI, as they dont provide any UI option to upload whole project at once.

You need to install git hub on your system and then you can upload your project using
shell/terminal/cmd.

To download git click here -->https://git-scm.com/download/win

Once it is installed, you need to create an git ccount or login to your git account if you already have.

and then go to repositories

create your new project repositories by your project name.


you will see this below:



, copy this line, you will need it.

git remote add origin https://github.com/Prittz/Test1234.git
git push -u origin master

Now, go to the project folder on your system.
and open terminal/cmd on that location.

and the run following commands:

Test1234>git init
Test1234>git add .     (note there is a dot (.) after "add") 
Test1234>git commit -m "first commit"
Test1234>git remote add origin https://github.com/Prittz/Test1234.git
Test1234>git push -u origin master  (note this would ask for username and password)



Done.
GO and check your web git hub.
Refresh your page.

Comments

Popular posts from this blog

Introduction to Reactive Programming in Java with Project Reactor

Introduction to Reactive Programming in Java with Project Reactor we will go through below: 1. Introduction to Reactive Programming What is reactive programming? Key principles of reactive systems: Responsive : Systems should respond in a timely manner. Resilient : Systems should be fault-tolerant. Elastic : Systems should scale as needed. Message-driven : Systems should use asynchronous messaging. Comparison between imperative programming and reactive programming. 2. Understanding Reactive Streams Publisher , Subscriber , Subscription , and Processor interfaces. The four key signals: onNext() , onComplete() , onError() , and onSubscribe() . Backpressure handling in reactive systems. 3. Introduction to Project Reactor What is Project Reactor? Key classes: Mono and Flux . Mono : Represents 0 or 1 item. Flux : Represents 0 to N items. Non-blocking nature and how it helps in building scalable systems. 4. Building a Reactive Application with Project Reactor Demonstrating how to use Mono ...

Camunda Spring Boot with Shared Engine with War file

This is the only one website (may be first) to show an example to create working war file for camunda shared engine using Spring Boot. We analysed the problem using pure spring boot "starter" dependencies that it contains camunda engine plus tomcat, so even when you remove tomcat using either <provided> or <exclude>, it continues to run on tomcat as its already with in camunda engine. And when you try to create war file and paste in into shared camunda engine outside then that war will no work. This is because that war you created containing camunda engine and a tomcat inside it and when you paste into another outside camunda engine, it gets confused to which camunda to use. Hence I worked on this and brought a mix version of spring and spring boot implementation of camunda. So here you go....and thanks me later :) Here is the pom file -------------------------------------------------------------------------------------------- <?xml version=...

Agentic AI – with Java (Spring Boot POC)

  This project is a simple Agentic AI Proof of Concept built using Spring Boot + Spring AI + OpenRouter (LLM) . It demonstrates how an AI Agent can investigate a problem step-by-step (like a human engineer) instead of following a fixed hardcoded workflow. 🎯 What Problem Does It Solve? Given a goal like: “Why is my Order API slow?” The agent will: Check system metrics Check database performance Check Kafka lag (optional) Correlate results Find the root cause Stop automatically 🤖 What Is “Agentic AI” Here? This is NOT a chatbot . This is: A state machine where an LLM is used only to decide the next step . The LLM: Does NOT access DB Does NOT access metrics Does NOT execute anything It only says: “Check metrics” “Now check DB” “Now we are done” All real work is done by Java code (tools) . 🏗️ Architecture (Simple View) User Goal ↓ Agent Loop ↓ LLM decides next action ↓ Java executes tool (DB / Metrics / Kafka) ↓ Result stored in memory ↓ Loop again until root ...