GitHabr: Its collective Habrahabr with blackjacks

First dive

I decided to start exploring the distributed version control system of GIT files from the Github web interface. Moreover, I was primarily interested in such a theoretical possibility: participation in the collective development of some small (but very responsible) project, without the need to install any additional software, limited to only the web interface accessible from any browser, and maybe with built-in notepad (for more comfortable editing of the source code).

Hypothetically, the entire project could at the same time be a single source code file, so that anyone could always get access to it, as well as, after making the changes, could send a request to the project manager to add the corrections to the main one (or alternative branch of the project.

Disclaimer

I’m not a real programmer, because I have never used a collective development environment, a version control system, or automated testing tools for my projects in my work, not to mention that I did not keep any working documentation (except, perhaps, most trivial comments inside the code).

Clearance

But, Here, that hour came when I began to realize how much I was deprived, and how my ability to create a truly high-quality product was limited.
My choice fell on Gitkhab.
Registration on Gitkhab is not just easy, but very simple:
')

Github

https://github.com/signup/free

Username: githabr Email Address: githabr@github.com Password: ******* Confirm Password: ******* 

By the way, during registration, you can also specify a fictional E-Mail address, since it is not verified in any way, and no confirmations and no mailings are sent to it. The main thing is that it is globally unique within the git hub.

Further, it is also easy to create a new repository for the project:

Githabr

https://github.com/new

 Repository name: habrahabr Description (optional):  [x] Initialize this repository with a README 

Installing the last checkbox will automatically insert a README file with Mark-Daun markup into the project.

Wiki jabry

https://raw.github.com/githabr/habrahabr/master/README.md

 habrahabr =========  

By the way, this file is then easily edited right on the site via a web form.

Seeing this opportunity, I quickly smiled on the fact that in this way you can publish the source texts of draft articles, which later will be published on Habré.
This is also the case, and after publication, it will enable anyone who noticed a typo or inaccuracy in the text to immediately correct the correction, so as not to litter the comments, and not to write to the PM. Moreover, such an opportunity will be available to absolutely any habrauser, including Read-Only contacts (which do not have the ability to write or write a comment), revealing many more opportunities to further improve the quality of the published material.

Actually, I suggest to transfer all habrapublications to open-source.

By the way, this is the question: how is it possible, in principle, on Habré you can show your draft of an article to a specific person (and, ideally, I would just like to open it to your friends from the list of added friends) before publishing it? Well, do not do the screenshots of the preview in fact!

My proposed approach to sharing the source code allows you to solve the preview problem by simply “feeding” the shared code to Habraparser, for example, through the same web interface of the Habr sandbox.

So, now let's try to pour something on the git hub:

Loading

https://github.com/githabr/habrahabr/downloads

 Upload a new file <> Choose a new file: c:\githabr\1.txt Short Description: test 

Everything. Now the file is available worldwide:

http : //cloud.github.com/downloads/githabr/habrahabr/1.txt

By the way, while it is distributed over the HTTP protocol (and not HTTPS), which has its advantages in some cases.

 HTTP/1.0 200 OK x-amz-id-2: 9CR8MvvocEfjYL/99TjOf2yPogURMenmPl/SVTfDwS8ForBAZ1+ahMY1BH3bm+LJ x-amz-request-id: D7AAFEFF905C59E4 Date: Fri, 08 Jun 2012 10:32:58 GMT Last-Modified: Tue, 05 Jun 2012 10:27:01 GMT ETag: "9fe7b2cc8b758cb05cd9dfbae8a825bb" Accept-Ranges: bytes Content-Type: text/plain Content-Length: 443 Server: AmazonS3 X-Cache: Miss from cloudfront X-Amz-Cf-Id: 0zpTMVSKtrVzBYTgxYS1RKFeVmcmHfj7a2LCIKwW3tvNK66tYhSN_w==,LQ9Uc46keGuXp2jnljH0SlmgtKFjenOn17raP2sYQckYh2fNg3HP2Q==,s7ibZDVHTSpJ0oGasHniYoU4QomnmfJ2x-3prHbYWfO4yi9PaGvgIQ== Via: 1.0 c1639d907cade557ebff29e5be78b0b6.cloudfront.net (CloudFront) Connection: close == 0zpTMVSKtrVzBYTgxYS1RKFeVmcmHfj7a2LCIKwW3tvNK66tYhSN_w, LQ9Uc46keGuXp2jnljH0SlmgtKFjenOn17raP2sYQckYh2fNg3HP2Q ==, s7ibZDVHTSpJ0oGasHniYoU4QomnmfJ2x-3prHbYWfO4yi9PaGvgIQ == HTTP/1.0 200 OK x-amz-id-2: 9CR8MvvocEfjYL/99TjOf2yPogURMenmPl/SVTfDwS8ForBAZ1+ahMY1BH3bm+LJ x-amz-request-id: D7AAFEFF905C59E4 Date: Fri, 08 Jun 2012 10:32:58 GMT Last-Modified: Tue, 05 Jun 2012 10:27:01 GMT ETag: "9fe7b2cc8b758cb05cd9dfbae8a825bb" Accept-Ranges: bytes Content-Type: text/plain Content-Length: 443 Server: AmazonS3 X-Cache: Miss from cloudfront X-Amz-Cf-Id: 0zpTMVSKtrVzBYTgxYS1RKFeVmcmHfj7a2LCIKwW3tvNK66tYhSN_w==,LQ9Uc46keGuXp2jnljH0SlmgtKFjenOn17raP2sYQckYh2fNg3HP2Q==,s7ibZDVHTSpJ0oGasHniYoU4QomnmfJ2x-3prHbYWfO4yi9PaGvgIQ== Via: 1.0 c1639d907cade557ebff29e5be78b0b6.cloudfront.net (CloudFront) Connection: close 

This file is displayed in the section
Manage Downloads

And, everything seems to be chiki-bunches, but one thing is incomprehensible: the file downloaded in this way got into the “cloud”, but not into the “master branch”. That is, unlike the README file, for some reason I don’t have the opportunity to edit it just as easily via the web form.

Well, okay: for this post, http://habrahabr.ru/post/145302/ I also uploaded its source to the cloud:

http://cloud.github.com/downloads/githabr/habrahabr/145302.txt

So what is next?

I don’t know what to do next. Can someone tell me with good advice?
I now need to somehow manage to attach this uploaded file to the workshop branch, and give anyone the opportunity to update it.

Links

How to start working with GitHub: quick start