You can clone with
HTTPS or Subversion.
Advise on how to help others.
Link about random order doesn't make any sense, added it to the chang…
Link to guidelines for interface text.
User interface text guideline added.
Note what has to be updated for new packages.
One developer tip.
Fix spelling mistake, thanks Ewoud.
Definition of done added to the docs.
Formatting and sequence of contrubution paragraphs.
Merge branch 'master' into gitlab-flow
Highlight the word master when referring to a branch name to make it …
…more obvious, thanks Ben.
Don't rebase pushed commits.
Insert at a random point in the changelog to prevent conflicts.
Merge branch 'small-contributions-no-rebase' into 'master'
Small contributions no rebase
Based on #7067 (comment)
Feel free to mention merge marshalls.
Use same size headers. Add PullReview. Mention shell guide as created…
… by us.
Document that we don't want pushed commits to be rebased and give a r…
…ationale for many small MR's policy.
Change the license to B.V.
Ask for small feature requests.
Nice trick for css class check mentioned by Dmitriy.
More strict wording of the bug criteria.
Merge branch 'what-is-a-bug' into 'master'
What Is A Bug
Ensure I can link to this line.
Features people are missing are not bugs.
We have html targets for paragraphs now.
Markdown doesn't render correctly yet.
Solve conflict and add more explanations on how to contribute.
Add style guidelines in separte paragraph.
Add note about not wanting unneeded options.
Ask people to link bakc and be prepared for feedback.
Change canonical urls to GitLab Cloud.
More hints for pull requests.
Separate procedures for both releases.
Accept our license agreement.
Rename support forum to mailing list to prevent duplication on commun…
…ity page of GitLab.org.