| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
|
|
|
| |
- This provides users with an easy to apply gitmessage template
for ease of seeing the commit guidelines here when they commit
against gitlab: i
https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#commit-messages-guidelines
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Some markdown headers needed tweaking to adhere
to standards, including blank lines above and below,
only one space after hash, first header should be
h1, and only one h1 per doc
|
| | |
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
|
| | |
|
| |
|
|
|
| |
Remove unneeded trailing whitespace in lines in
/development /ci /api and /administration docs.
|
| |
|
|
|
|
| |
Updating redirected links in the development, install, policy
raketasks and university dirs. Should now link to final
URL to avoid redirect hops
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing square brackets, links, etc in:
merge_requests.md
vulnerabilities.md
issues.md
issues_statistics.md
pipelines.md
services.md
group_milestones.md
milestones.md
runners.md
changelog.md
issue_workflow.md
elasticsearch.md
api_graphql_styleguide.md
automatic_ce_ee_merge.md
file_storage.md
architecture.md
database_debugging.md
index.md
index.md
frontend_testing.md
pry_debugging.md
vue.md
development_process.md
|
| | |
|
| |
|
|
|
|
| |
After review, heading was changed and links to
it needed to be updated, and minor tweaks to
the issues docs such as note formatting
|
| |
|
|
|
| |
Based on https://about.gitlab.com/handbook/product/categories/#release-stage:
- 'core release' -> 'progressive delivery'
- 'supporting capabilities' -> 'release management'
|
| | |
|
| |
|
|
| |
Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
|
| |
|
|
|
| |
Mentions the automatic inference of stage and group labels based
on the applied subject labels
|
| | |
|
| | |
|
| |
|
|
|
| |
Also adds and one linting rule
and makes project conform to it.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Apply review turnaround time to community contributions
See merge request gitlab-org/gitlab-ce!28233
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The new version requires `python3` to be available. In omnibus
installation this is already a reality as we are currently pathing
previous `gitlab-markup` version to use `python3` instead of `python2`.
We are now requiring `python3` with the gem without having to patch it.
As a consequence to also make it easy to use it in development, we've
introduced a `Pipfile` and `Pipfile.lock`, working similarly to
`Gemfile` and `Gemfile.lock`, and added documentation on how to use
them.
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.
For consistency, also ensure entries in the list
are aligned when they span multipls lines.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.
Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.
A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.
This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).
|
| |\
| |
| |
| |
| | |
docs: GitLab uses group milestones to handle issues
See merge request gitlab-org/gitlab-ce!24953
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Update source installation to make it easier for release managers to work on releases
Closes gitlab-org/release/framework#113
See merge request gitlab-org/gitlab-ce!24967
|
| | |/
| |
| |
| |
| |
| | |
This adds a small line to the MR workflow to clarify that new source
installation requirements have to be added when they are introduced,
instead of release managers having to add them.
|
| |/ |
|
| | |
|
