llllvvuu
commented
8 years ago Sure why not. There are some simple github conventions we can follow or not follow:
- one branch per logical change
- one commit per branch most of the time (via commit --amend or interactive rebase. definitely don't need to do this 100% of the time)
- reasonably named branches (feature/name-of-feature or bugfix/issue-number-or-description-of-bug)
- reasonable commit messages (72 character wrapped, written in imperative form; one summary line followed by blank line followed by paragraph/bullets detailed, unless change is trivial. if fixes an issue make the summary line "Fix #NUM.")
- either pull request directly into master or have a branch in between (e.g. have PRs go to dev, and occasionally PR dev to prod/master).
- merge a PR when at least n people are ok with the change
- tests and continuous integration LMAO jk
There's no need to use forks. Everyone should have push access here. It's just nice to use branches and PRs (from this repo to this repo) anyway so people can see what's been going on.
tttmmmiii
enitiz
I'm just learning love/lua, maybe others are too, and this is my first time working withothers on github. I was thinking of starting a tutorial branch but I'm not sure if it'd be pointless or confusing or what. In general I do like the idea of branches, especially having stable/development branches.
I think I'll just go ahead and make it, because why not. Respond if there are any arguments against, or any other organizational issues.