githelp.co.za - you are welcome

[Thor]

Had a empty domain.

Placed a few git references up on it until I figure out what to do with it.

If any of you are git guru's and want to make tutorials or contribute in any way or have ideas feel free reply

In the meantime while the domain has no purpose enjoy the Git cheat sheet

http://githelp.co.za/


Github Repo for GitHelp.co.za

 

[rward]

Step 1: Use the CLI

 

[rward]

Why isn't the page in git?

Then you can accept pull requests.

 

[Thor]

Why isn't the page in git?

Then you can accept pull requests.

That is a neat suggestion.

I am a noob.

You want me to take the Page Source and put it on github and then others can work on it and push back into the main branch and then I take the latest main version and update the code on the website

Am I understanding correctly?

 

[_kabal_]

you can also use git pages, and setup custom domain.


then you just always deploy master, and any pull request that are merged back into master will automatically available

 

[Thor]

you can also use git pages, and setup custom domain.


then you just always deploy master, and any pull request that are merged back into master will automatically available

True, but I am afriad github pages might limit our potential as its only static jekyll I think. Iirc.

The server has other goodies like databases whoop whoop

 

[[)roi(]]

git --help

 

[Chevron]

 

[Thor]

Right here it is:


Github Repo for GitHelp.co.za

Please note I am a github noob, I attempted the Readme file

The code itself is very bad (I was rushing to get it up)

As for the rest, well feel free to make something wonderful.

 

[Hamster]

Step 1: Use the CLI

This

 

[Thor]

This

I don't understand.

I thought cli is the command line?

Remember everyone got on my case last time for using the GUI git app instead of using git in CLI in other words what relevance does this have on git itself? or am I missing something?

 

[DrJohnZoidberg]

No rebase

 

[[)roi(]]

Same thing; command line interface. The commands you type in a command prompt and/or terminal.

 

[Thor]

No rebase

Fork it, edit it, push it

Then bam! Rebase is added in the cheatsheet

 

[Hamster]

Fork it, edit it, push it

Then bam! Rebase is added in the cheatsheet

Done

 

[Thor]

We have a FORK!!

Omg omg omg omg

I did not think it would happen

I don't know what to do now?

Do I just say merge pull request?



What is the best practice here, how does one handle the main branch to ensure this merge does not break it or preview it etc?

 

[herbertk]

No rebase

Makes me sad also...

 

[shadow_man]

Nice idea. Loving the way you're adding in your domains.co.za affiliate link on the sly

 

[Hamster]

We have a FORK!!

Omg omg omg omg

I did not think it would happen

I don't know what to do now?

Do I just say merge pull request?

View attachment 376678

What is the best practice here, how does one handle the main branch to ensure this merge does not break it or preview it etc?

Lots of different ways. Me?

Master = production/live
Integration/Development = set of feature work that's approved and waiting to be merged to master
feature/whatever = created from master, dev done in there, pull/merge request sent to integration once done

 

[Hamster]

Now click the merge pull request button and give us rebase