issues vs pull requests / new branches

[mikecflynn]

Hey Linus,

Being a newbie on github I'm not sure the best way re communications. Is this the way, i.e., with Issues? I also thought maybe to create a new Branch where I could post stuff that wouldn't effect the Master Branch.

I guess if I don't hear back then this Issue is probably not the best way to go :)

Mike Flynn

[IgnoredAmbience]

Recommended route for code contributions is to "Fork" the repository, create your own branches there, and use them to raise "Pull Requests" with the new code. Overall features and plans should be discussed in appropriate issues on the main repository (here).

[mikecflynn]

That makes sense and I read it somewhere too. Actually, I tried to do just that though without success. I thought (though only an educated guess - I only briefly looked over the helpme guide) maybe I didn't have permissions or the like? Is anyone simply allowed to make changes to Github projects? I'm guessing there must be a facility to restrict access, etc. Like I say though, I'm a complete newbie and didn't want to end up doing anything silly.

As for the actual project itself I must admit to having second thoughts. It can sometimes be a whole can of worms with this kind of collabaration kind of thing, especially with the lack of knowledge I have, not just on github, but also Gherkin and BDD. Anyway, if no-one minds I'll certainly look back and see whether there is something I can contribute?

Cheers :)