Primary Class a

https://www.youtube.com/watch?v=_C5AHaS1mOA

Bootcamp Day 1 - Template for README.md, you can use in your repo Originally, README.md was just for letting know, what's in your project. Now, people have found its new use case just for chapter compilation, like what we are doing in Chapter 1 and ahead

Template files for writing maintanable GitHub projects. Make your repo pretty!

So you had an idea and developed the next world’s industry-changing application. You decided to open-source it because you’re way cool. Now you need to educate people about your project and need some docs to get started. You write that here. :alien:

Templates included: • PULL REQUEST TEMPLATE • ISSUE TEMPLATE FOR FEATURE YOU MORE WANT • ISSUE TEMPLATE FOR BUG YOU FIND

Installing

Clone this project and name it accordingly:

git clone git@github.com:sbibek086/Git-and-Github-Guides.git MY-PROJECT-NAME && cd MY-PROJECT-NAME

Getting Started

This project is a collection of boilerplates with CONTRIBUTING and CONTRIBUTORS documentation. It also includes a basic ISSUE_TEMPLATE and PULL_REQUEST_TEMPLATE. All templates are filled under .github/ folder.

Usage

1. After installing, remove this file rm README.md.
2. Move the README template file located under .github/ to the main directory mv .github/README.md . :cool:
3. Follow the basic usage guidelines in each file or make it your way. The world is yours.

CHANGELOG References

This boilerplate intentionally did not provide any CHANGELOG file as example, since this tool could make it automatically, fulfilling the file’s objective.

Contributions of any kind welcome!

License

To the extent possible under law, sbibek086 has waived all copyright and related or neighboring rights to this work.

Reserve your seat by filling in form below:

फुल क्लास प्याकेज शुल्क - रु ७००० मात्रै

समय: बेलुका ६ देखि ७ बजेसम्म

८ कक्षा भन्दा माथि देखि SLC, +2 दिएर बसेका हरुलाई उपयुक्त

अवधि: 30 वटा क्लास

शनि, सोम, बुध र शुक्रबार

Requirement: At least 2.8 and above GPA in SEE

रोजगारको प्लेसमेन्ट पनि गरिनेछ, पर्फमेन्स उत्कृष्ट गर्नसक्नु भएमा ।

Bootcamp Day 2 - Github Flow of commands

माथिको चित्रमा रहेको कमान्डको सिक्वेन्स केवल git remote प्रयोग गर्दा मात्र गर्ने हो। यद्यपि, जब तपाइले github प्रयोग गर्दा, githubमा GUI बटनहरू हुन्छन् जसले तपाइलाई कुन पछि कुन गर्ने भनेर देखाउँदै जान्छ। त्यसैले github प्रयोगकर्ताले कमान्डको सिक्वेन्स सम्झनु पर्दैन।

त्यसैले, वास्तविक कामको अवस्थामा, स्टिक फिगर चित्रमा देखाए जस्तो, तल रहेको वर्कर A ले माथिको worker B लाइ नया संस्करण पठाउनु पर्दा, bash अर्थात् टर्मिनल अर्थात् command promptमा यसरी लेख्नुपर्ने हुन्छ:

git add .

git commit

git push origin master

किन? किनकि उसले आफ्नो लोकल मेसिन या नी की आफ्नो कम्प्युटरमा (अर्थात् MASTER repo या नी की File मा) README.md थपेर बनाएको नयाँ संस्करणलाई originमा push गरिरहेको छ। सरल भाषामा भन्दा, उसले MASTER बाट ORIGIN (मेरो github repo) मा नयाँ संस्करण धकेलिरहेको छ।

PS: orgin मेरो-मेसिन म या नी की यो प्रसंगमा worker B र र master नाम उसको स्थानिय मेसिन रिपो या नी की worker B को लागि पूर्वनिर्धारित नामहरू हुन् र यसलाई github remote add origin url द्वारा अन्गय नाममा भने change गर्न सकिन्छ।

माथिको चित्रमा, सधै दुई जना चित्रित व्यक्तिहरू, रियलमा दुइजना नहुन सक्छन्। - जस्तो की म आफैं (तलको Worker A)ले मेरो स्थानिय मेसिनबाट, (माथिको Worker B)मेरो गिटहब रेपोमा push गरिरहेको हुन सक्छु।

अब यसलाई यस्तो परिस्थितिमा हेरौं कि Bob ले मेरो github रेपो देख्छ। उसले यसलाई github . com/Bob/BibeksPrj मा github fork गरेको छ र graphics feature परीक्षण गरी मर्ज या नी की थप्न खोजेको छ भनेि (उसले मलाई आफ्नो थपेको काम, मेरो रेपोमा PULL गर्न अनुरोध गरिरहेको छ) उसले मलाई PULL REQUEST submit गर्छ।

त्यसैले मेरो graphics repo मा, उसले थपेको संस्करण पुल गर्न या नी की ल्याउन, मैले मेरो command prompt मा लेख्नुपर्छ: git pull Bob Graphics

माथिको कमान्डको मतलब, Bob को रिपोबाट, मेरो मास्टरमा नभई, मेरो मेसिनको GRAPHICS branchमा मैले PULL गर्दैछु।

उसले थपेर दिएको कामको रिजल्ट मैले मेरो google chrome browser मा कम्पाइल भएर खुल्दा रिजल्ट भनेजस्तै ok छ भने मैले -

git commit -m

त्यसपछि, git checkout master - यसले GRAPHICS शाखाबाट मेरो MASTER शाखामा स्विच गर्न

त्यसपछि, git merge graphics - यसले GRAPHICS शाखाबाट परिवर्तनहरू मेरो स्थानिय मेसिनको मास्टर शाखामा मर्ज गर्छ

त्यसपछि, git push origin master - यसले अन्तत मेरो गिटहब रेपोमा परिवर्तनहरु प्रतिबिम्बित गर्नेछ

सम्झिन सजिल’री चाहनुहुन्छ भने PUSH TO, PULL FROM भनेर सम्झिनुस् है, जसको मतलब

git push origin master means push TO origin from master

git pull A B means pull from A to B .

Bootcamp Day 3- How Tester uses git?

अबको तलको प्रसङग्, मैले IT कम्पनी -YIlab मा परीक्षणकर्ता या नि की ‘टेस्टर’को रूपमा काम गर्न थालेपछि लेखें। त्यसैले, यो टेस्टरको दृषटिबाट तल अनुसार गर्नुपर्छ:

अब म परीक्षणकर्ता हुँ।

अर्थात्, माथिको कथा पुसर अर्थात् विकासकर्ताको दृष्टिकोणबाट थियो, जसले केही सुविधाहरू थप्छ र मर्जर अर्थात् Chief Technical Officer CTOलाई production अर्थात् लाइभ सर्भरमा मर्ज गर्नका लागि बुझाउँछ।)

तर, अब म परीक्षणकर्ता हुँ, जसले विकासकर्ता या नि की ‘डेभलोपर’बाट, सबैभन्दा पछिल्लो संसोधित काम मात्र आफ्नो कम्प्युटरमा तान्छ या नी की pull** गर्छ र परीक्षण गर्छ, ता की CTOले त्यो काम मर्ज गरोस् ।

**म टेस्टरले आफ्नो कम्युटरमा, pull command गर्दा, ( मास्टर branch या नि की tested-Ok-feature-branch-मर्ज-गरिएको branch मात्र pullभएको हुन्छ भन्ने गलत बुझाइ मेरो थियो ) तर पुरै भएभरका branchहरू पुल भएका हुन्छन्

अब निम्न अनुसार गर्छु:

पहिला: git pull (git pull प्रत्येक दिन गर्नु पर्छ किनभने प्रत्येक अघिल्लो दिन, CTOले विभिन्न शाखाहरूबाट नयाँ परीक्षण पास भएका ‘फिचर’हरू - जस्तै अपडेटेड .env मर्ज गरेको हुनसक्छ अघिल्लो दिन)

सामान्य दैनिक काममा यो नबुझे पनि चल्छ तर कहिलेकाहीँ यो नबुझे ठुलो दुर्घटना झंझट हुनसक्छ।

git pull लाई डिफल्ट रूपमा git pull origin develop(<- remote) which means transfer from Master aka remote branch to Main aka local branch बुझिन्छ ।

दोस्रो: git checkout -b "feature/ translationToEnglish" (यहाँ म त्यस ब्रान्चमा स्विच गर्दैछु {हो, मेरो लोकल मेसिनमा भएको translationToEnglish शाखा, जहाँ translationToEng काम थपिएको छ

त्यसपछि, म यसलाई स्थानिय रूपमा या नि मेरो लोकल मेसिनमा डिप्लोय गर्छु (npm run या yarn dev आदि आदि) ताकि उसको काम - translationToEng सही छ कि छैन हेर्न। मैले जाँच गर्दा काम ठिक छ भन्ने पाएपछि म यसलाई push गर्न चाहन्छु

तेस्रो: git add --all (यहाँ हामी git add –all गर्छौं र मात्र git add . गर्दैनौं । यसको कारण छ, जुन मैले मेरो ब्लगमा लेखेको छु)

चौथो: git commit -m "feat: added static translation" // यदि सबै ठीक छ भने, यसले दिन्छ - WORKING TREE CLEAN

पाचौं: git push

‍‍‍‍‍‍===after being employed as tester in YI===

origin—v0.0.1 —v0. 0.2 —if after this coming one patch fixed makes it stable in live, then v0. 1.0

AlexWorkingOnNewFeatureBranch–v0. 0.1–v0. 0.2 of this branch

BobWorkingOnTranslationBranch—–

etc etc.

now if I pull from origin, then not only origin branch but also with AlexWorking.. Branch IE. whole tree comes to my local.

now, git pull just pulls latest v of branch I am in, which known by git status

but git fetch –all pulls aka fetchess latest version NOT only from current branch but from all branches .

Before that, ‘pull’ should be preceeded by yarn or npm or.. depending on situation because packages dependencies might have been pushed to origin by Origin-er, which might be gitignored and we should in local also install and its info paths etc already in package.json and /or package-lock.json

Above is very very important concept so, shouldnt be forgotten.

git stash is ‘chhupake rakhna’ means you neither commit n push nor u save it in ur repo publicly. it’s just there for u to see, n this change won’t be committed either, when u commit push this repo.

*Beginners think they should install that seperate git CLIs but they are wrong. 
All you have to do: goto Terminal in Vstudio , then in its terminal, point directory to ...xampp/htdocs
so that you can clone git remote urls docs inside htdocs.

So, after that you can change it to see its compilation result in browser,
at the same time, can change, commit etc to reflect changes in git ready docs.*

One thing Now Pro me have to suggest to this amateur me's this paragraph is: I dont need to put it in xampp htdocs to init server for every language (its necessary for php developing). Eg. In react, to initialize server, i just have to write: npm start as server initialization is implicitly handled by package.

Bootcamp Day 4- Whats upstream policy and why its used in IT workplace + Why Gitlab, NOT github is used in Nepal?

In real IT workplace, workflow looks like below:

< Visual tour of gitlab will be done in class & its edge over github will be explained >

Bootcamp Day 5- Real Painful scenarios I faced, abd how to understand fix it?

So, in production aka development day yesterday morning , I had pulled from say predevelop branch, then deployed. now today evening, predevelop branch has been lot + - by now, then obviously, I need to

git pull origin predevelop

today too

/so, i wasnt aware that predevelop develop etc branch exists in my local universe as is in remote universe, which I thought to only exist. silly me} . ANYWAY more on that lateron but 1thing for sure- when I do git status, it is showing which branch I am on, in local universe/

So, today I do as I mentioned earlier git pull origin predevelop

lots more packages might have been added by production devs by today

so, we will get all warnings like-INCORRECT PEER DEPENDENCY

1st, lets understand about package dependency & then we will return to main context

Ok, lets return to main context: WHY? because packages that i had pulled yesterday, lots packages might have been added by production devs

So dont worry- Just remove old package-lock.json , NOT package.json tho. Then do

yarn

It will freshly install packages

– package.json - Now, I understand why package.json should be there because it shows packages versioning that my program is using

WHY this package-lock.json?

Bootcamp Day 5 - Breaking down Settings Panel of each Github repo

Bootcamp Day 6 - Assets aka output files of Github repo

Most of the assets in Github repo are either in .tar or .Linux or .mvcc.zip or gnu.zip.

• mvcc stands for Microsoft Visual C++ compiler ,and is native in typical Windows OS. Also, If I unzip mvcc.zip, there’s SHA256 file inside it.
• Gnu.zip works in Windows OS that has GNU compiler.

Did you know that UNIX OS are designed to do just one thing better. Windows OS revolted against such specific purpose but were proprietary locked but LINUX also revolted against such UNIX style specific purpose and were Open source..

Bootcamp Day 7 - Permission levels of different Roles in Personal repo (Organization Repo not covered)

Here is its official docu. We hope to convey this information little easier

Bootcamp Day 8 - Developer Settings in Github Here, we are not talking about what your SSH or GPG keys of your github account should be? tara ssh token aka keys vannu ra ya kura gareko personal access token vannu eutai ho

But for now, we are talking about settings that you can adjust lot wholesome way like with scripts, rightly called Developer Settings,

Let’s start with Personal Access tokens: This Video would help too.

a)Secret Key: Used to sign/encrypt data for secure communication. Its type:

• Access Token: Grants temporary access to protected resources (e.g., OAuth 2.0).
• Refresh Token: Used to obtain a new access token without re-authenticating.
• JWT (JSON Web Token): A specific type of token that contains claims and is signed for integrity. b) Token: Authenticates users or sessions for resource access. eg. esewa euta tab ma login garda arko tab ma ni send mony etc garna painxa wa yei PAT jasto c) API keys: yo prasanga ra a) ra b) vanda alag ho but IKnowIt

For eg: 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37 is my sbib Personal.Access.Tokens of github acc as github has stopped supporting acc passwords. Now it requires token-based authentication (for example, a personal access, OAuth, or GitHub App installation token) for all authenticated Git operations.

e39de365649162ec365f7a88b0f6e571e6d23c7268 is my sbib github package personal access token with read write and repo rights. tara yo pani after certain time expire hunxa I think because email ma yo expire vayo vanee aairako hunxa

.github folder vitra ka kura localMachine bata git transfer hudaina. myMachine secret keys, local environment vars haru hunxa es vitra

Bootcamp Day 9 - Setting up Public template as new repo template, Speed vs Inflexibility, which to opt for?

Now, it gives me question of what exactly is difference between public template and boilerplate? Currently, my understanding is: boilerplates are like templates which already has Layer 0 folders required for adding up next layer application logic folders.

Bootcamp Day 10 - Working with Boilerplates - Problems faced and its solutions: Boilerplate repos are great way to speed up dev process - lot faster than w sdk ways but it can be difficult to learn.

Stuck with this Host key verification failed error

Problems: I was quite lost with whether github username password that I have passed in my machine is still stored in cache & whether thats creating trouble as I have changed github.com password ever since between. git config --global username.password <> do not seem to be much of rescue tho. My intention was to so that I could feed my newly github password to my machine.

Above, I was doing the way of git clone https:// way but SSH way is better

Solutions: github has stopped supporting acc passwords. Now it requires token-based authentication (for eg, a personal access, OAuth, or GitHub App installation token) for all authenticated Git operations. Excerpt from:https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/

this says what we should do.

But when we visit this, `we see it says to update iCloud Keychain’s github pws, WHY?

because brave lets u store pws for online accs, NOT for localmachine pws like in this case pw stored aka cached in localmachine that for github- its assuming user is Mac-er & hence iCloud should be there by default but since for Asian windower like me, closest thing we can get is install ‘iCloud For Windows’ in Windows.`

and after installing iCloud App, it says to setup Windows Hello Pin and hence below screenshot

this seems to answer this above issue.

Bootcamp Day 11- This repo itself is Template repository

Have I solved Bootcamp Day 10’s issue with this method is beyond scope of now, however lets not delete Chapter 7. But this is Template repo itself as you can see ‘Use this Template in upper belt navigation, which doesnt come for normal repo’ Just use it as template- the root layer file structure will be duplicated in your new github repo.

Bootcamp Day 12 - Environments, while you go to settings in repo. What are they?

https://youtu.be/nI6pRfH7VTc

Bootcamp Day 13 - Which open source license to use when? https://choosealicense.com/

Bootcamp Day 14 - what to do with submitted issues in project board