Skip to content

Commit d50bfcf

Browse files
authored
Update README.md
1 parent 8748e73 commit d50bfcf

File tree

1 file changed

+1
-224
lines changed

1 file changed

+1
-224
lines changed

README.md

Lines changed: 1 addition & 224 deletions
Original file line numberDiff line numberDiff line change
@@ -1,224 +1 @@
1-
# whats up idiots
2-
3-
# TRANSITION TAYO SA NEXT AIGHT?!
4-
5-
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
6-
7-
## Getting Started
8-
9-
First, run the development server:
10-
11-
```bash
12-
npm run dev
13-
# or
14-
yarn dev
15-
# or
16-
pnpm dev
17-
# or
18-
bun dev
19-
```
20-
21-
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
22-
23-
You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
24-
25-
This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.
26-
27-
## Learn More
28-
29-
To learn more about Next.js, take a look at the following resources:
30-
31-
- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
32-
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
33-
34-
You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
35-
36-
## Deploy on Vercel
37-
38-
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
39-
40-
Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
41-
42-
## Set up git mothafucka
43-
44-
Rinespeto na nga kita eh. Pero anong ginawa mo? Tiger. Tiger, alam ko pero hindi ako rinespeto tiger. Isipin mo 'yon, tiger. Hindi ako rinespeto tiger. Mukha lang akong makasalanan, mukha lang akong lasinggero. Pero ginawa akong lasingero! Tiger isipin mo 'yon. Isipin mo 'yon, tiger. Ginawa akong lasinggero ng titser na yan?! Ha?! Ano?! Ginawa akong lasinggero niyan... pare isipin mo 'yun tiger. Ginawa akong lasinggero ng tarantado na 'yan. Isipin mo, tiger, isipin mo! Tignan mo! Tiger... Tiger hindi ako lasing. Tiger hindi ako lasing.
45-
46-
okay first things first, we need to install git in your machine.
47-
here's the [link](https://git-scm.com/downloads)
48-
49-
now you'll need to open your git bash terminal para cool; pero pwede naman kahit anong terminal.
50-
51-
so now we'll need to set up your information in your machine para alam ni git where to send your code, llike which account
52-
53-
so you'll need to input these commands; you'll need to have your github accounts set up before doing these steps.
54-
55-
```bash
56-
$ git config --global user.name "(your name in github)"
57-
$ git config --global user.email your.email@example.com
58-
```
59-
60-
Replace "your.email@example.com" with your GitHub email. now na na-input na natin mga shit na yan run
61-
62-
```bash
63-
$ git config --list
64-
```
65-
66-
and check if tama ba information
67-
68-
## Dev env
69-
70-
okay since we're gonna be doing some web development let's install Node sa machine nyo
71-
72-
[Node.js](https://nodejs.org/en/download)
73-
74-
and with that mag kakaron na tayo ng shit we call npm and yes lahat ng natutunan sa comp org is gagamitin natin; yyung cli commands
75-
76-
tangina visual studio tayo ha.
77-
78-
## Dev
79-
80-
anw since may version control na tayo lets clone the repository sa github
81-
cloning is basically fetching the code sa github
82-
respository is the place were all the project's files are stored
83-
84-
so by now I've probably asked you to send me your email para ma add ko kayo as collaborators sa repository. So what you'll want to do is to go to the repository and open your terminal.
85-
86-
make a directory for our project in your system
87-
88-
```bash
89-
$ mkdir studyHub_system
90-
```
91-
92-
or what ever folder name you want
93-
94-
tapos navigate tayo don with
95-
96-
```bash
97-
$ cd studyHub_system
98-
```
99-
100-
so habang nasa loob na tayo ng project directory what you'll want to do is punta sa repository natin sa github and click yung code button na color green and copy the link there, tthen run this command
101-
102-
```bash
103-
$ git clone link
104-
```
105-
106-
replace "link" with the link na na-copy nyo
107-
108-
then tada!!!!
109-
110-
so ofcourse we'll be regularly pushing code sa repository and hindi automatically ma update yung sa local version nyo
111-
112-
## Pushing and Pulling Code
113-
114-
Now that you've cloned the repository, let's talk about how to keep your local copy of the code in sync with the remote repository on GitHub.
115-
116-
## Branches
117-
118-
So syempre here's the one of the main reason why we're using git. para we can work on different parts of the code without affecting the master branch which is what is in production. So we'll be creating branches for each of you and you'll be working on that branch. So when you want to push your code you'll need to push it to your branch and not the master branch.
119-
120-
### Creating a Branch
121-
122-
```bash
123-
$ git checkout -b branch-name
124-
```
125-
126-
so ayan na create na natin yung branch nyo and you'll be working on that branch. So everytime you want to push your code you'll need to push it to that branch.
127-
128-
### Switching Branches
129-
130-
```bash
131-
$ git checkout branch-name
132-
```
133-
134-
so if you want to switch to another branch you'll need to run this command
135-
136-
and syempre mga idiots tayo sobrang daming branch na magagawa so you'll need to check what branch you're currently working on
137-
138-
```bash
139-
$ git branch
140-
```
141-
142-
and it will show you the branch you're currently working on and the other branches
143-
144-
so para maiwasan narin yung magulong tree, everytime we complete a task we'll create a branch specific for that task and after we're done with that task we'll merge it to the master branch and close it.
145-
146-
command is
147-
148-
```bash
149-
$ git branch -d branch-name
150-
```
151-
152-
replace "branch-name" with the branch you want to delete
153-
154-
### Pushing Code
155-
156-
When you make changes to the code and want to share those changes with others or save them to the remote repository, you'll need to push your code.
157-
So that di nyo masira yung master branch which is what is in production.
158-
159-
so here's the command
160-
161-
```bash
162-
$ git add .
163-
#so we're staging the changes we did to the code. the '.' represents everything in the directory that has been changed pero pwede naman specific files lang
164-
165-
$ git commit -m "message"
166-
# Commit your changes with a descriptive message para di naman super confusion ano pinupush nyo code
167-
168-
# Push your changes to the remote repository
169-
$ git push origin master
170-
```
171-
172-
Replace "master" with the branch youre working on.
173-
174-
And after all that syemmpre I'll be the one to merge the code to the master branch para di naman magulo and di nyo masira yung master branch so you'll need to go to github and create a pull request on your code. Pag ka open nyo ng repository natin sa github may makikita kayong button na "pull request" and click nyo lang yun and follow the instructions there.
175-
176-
## Pulling Code
177-
178-
syempre everytime mag start ka mag code and before mag push ng code you'll to make sure na latest yung code sa local machine mo so you'll need to pull the code from the remote repository.
179-
180-
```bash
181-
$ git fetch origin master
182-
# Fetch the latest code from the remote repository
183-
184-
$ git merge origin/master
185-
# Pull the latest code from the remote repository
186-
187-
```
188-
189-
again replace "master" with the branch youre currently working on.
190-
191-
## Merging Code
192-
193-
So syempre we'll be working on different parts of the code and we'll be merging it to the master branch. So everytime you want to merge your code to the master branch you'll need to create a pull request on github. So pag ka open nyo ng repository natin sa github may makikita kayong button na "pull request" and click nyo lang yun and follow the instructions there.
194-
195-
## Attendance
196-
197-
Ramos, Eric - Done
198-
199-
poem by borat
200-
201-
In Kazakhstan, where sky so blue,
202-
My mankini shines, my thong so true.
203-
With hairy chest and crooked smile,
204-
I'll make you laugh, just for a while.
205-
206-
I travel far, both near and yon,
207-
To find the humor in everyone.
208-
From fancy cities to the wild, wild West,
209-
Borat's adventures are the zaniest, at best.
210-
211-
I wrestle with gypsies, in muddy delight,
212-
And ask strange questions in the middle of night.
213-
My accent, it's thick, like molasses in snow,
214-
But I'm Borat from Kazakhstan, don't you know?
215-
216-
I bring a mirror to reflect your quirks,
217-
And uncover your biases, with comedy that works.
218-
With my camera in hand, and a notepad too,
219-
I expose your prejudices, it's what I do!
220-
221-
So raise a glass, a shot of Kazakhstani brew,
222-
To Borat, who'll always make you giggle and woo.
223-
In a world so nutty, in satire we jest,
224-
I'm Borat, from Kazakhstan, and I'm the best!
1+
needs update

0 commit comments

Comments
 (0)