gitlab-org--gitlab-foss/doc/workflow
Robert Speicher 9f7a7115a4 Convert CHANGELOG to Markdown
All this does is convert the version sections into headers. The list
items shouldn't really be indented by two spaces, but it makes no
difference to the rendering and this way we retain authorship history
for the actual changes.

Related to https://gitlab.com/gitlab-org/release-tools/merge_requests/29
2016-10-16 21:05:24 +02:00
..
add-user
forking
groups
img
importing
lfs
milestones
notifications
releases
authorization_for_merge_requests.md
award_emoji.md
award_emoji.png
cherry_pick_changes.md
ci_mr.png
close_issue_mr.png
environment_branches.png
file_finder.md
forking_workflow.md
four_stages.png
git_pull.png
gitdashflow.png
github_flow.png
gitlab_flow.md Convert CHANGELOG to Markdown 2016-10-16 21:05:24 +02:00
gitlab_flow.png
good_commit.png
groups.md
labels.md
merge_commits.png
merge_request.png
merge_requests.md
merge_when_build_succeeds.md
messy_flow.png
milestones.md
mr_inline_comments.png
notifications.md
production_branch.png
project_features.md
protected_branches.md
README.md
rebase.png
release_branches.png
releases.md
remove_checkbox.png
revert_changes.md
share_projects_with_other_groups.md
share_with_group.md
share_with_group.png
shortcuts.md
timezone.md
todos.md
web_editor.md
wip_merge_requests.md
workflow.md