Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-04-15Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-04-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-30Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-10Fix broken link to the handbookDavid H. Wilkins
- Broken link to "How to work with the distribution team"
2019-09-04What to avoid in code reviewMarin Jankovski
2019-09-03Add Danger bot development documentationNick Thomas
This is overdue, and some of the suggestions are embarrassing, but this is how we actually develop Danger today.
2019-07-25Add a section of examplesKerri Miller
We have a fairly good guide to Code Reviews, but can be improved by adding a few examples of what a good code review looks like at GitLab, specifically ones where there is a bit of back and forth, "nit-picking," etc. This would: + help set expectations of newly hired engineers around what our process looks like when it is functioning what level of scrutiny their code will be under + how we have technical conversations + show by example how after you're done crafting a solution, there can still be extra work done either tidying up code and/or managing the communication and conversations about your proposed MR
2019-07-19Document database review processToon Claes
See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
2019-07-19Update numbered lists for docs standardsMarcel Amirault
Ensure that all numbered lists use only 1. and no other numbers. Also ensure that numbered lists use proper spacing.
2019-07-18Fix unordered list spacingMarcel Amirault
Correct the spacing of unordered markdown lists in docs, to maintain standards of documentation.
2019-07-15Rename "discussions" to "threads" in docsMichel Engelen
2019-07-09Update the installation linkCindy Pallares
The installation link has changed from /installation/ to /install/. This commit will update all the remaining links that are missing.
2019-06-24Require database reviews for migrationsAndreas Brandl
2019-05-27Use relative URLs in development docsAchilleas Pipinellis
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
2019-04-30Give reviewer roulette its own header in the docsSean McGivern
2019-04-16Refer to guidelines on when to assign MRs close to the freezeDouwe Maan
2019-04-16Rewrite "Review turnaround time" sectionDouwe Maan
2019-03-25Add ssot link to security reviews documentationJames Ritchey
2019-02-21Apply suggestion to doc/development/code_review.mdMarcia Ramos
2019-02-21Update code review guidelinesMarcia Ramos
2019-02-18Merge branch 'docs/zj-reviewer-guidelines' into 'master'Nick Thomas
Add a soft SLA for reviewers and maintainers See merge request gitlab-org/gitlab-ce!25192
2019-02-18Improve languageZeger-Jan van de Weg
2019-02-13Reviewer roulette via DangerNick Thomas
Make danger pick reviewers and maintainers at random, for feontend, backend, database, etc, changes, whenever files belonging to those teams get changed.
2019-02-13Add a soft SLA for reviewers and maintainersZeger-Jan van de Weg
By setting expectations both the contributor and reviewer have more certainty on what gets reviewed when, and at what speed changes could be merged.
2018-12-11Fix links to sections that were movedMichael Kozono
2018-11-30Fix Red/Orange data link markdownPhilippe Lafoucrière
2018-11-29Merge branch ↵Rémy Coutable
'docs/8608-update-approval-guidelines-to-include-red-orange-data-reviews' into 'master' Add RED data security requirement to code review See merge request gitlab-org/gitlab-ce!23426
2018-11-29Merge branch 'mk/author-preparation-docs' into 'master'Marcia Ramos
Encourage MR author preparation in Code Review Guidelines documentation See merge request gitlab-org/gitlab-ce!23360
2018-11-28Add RED data security requirement to code reviewPhilippe Lafoucrière
closes #8608
2018-11-28Encourage MR author preparationMichael Kozono
2018-11-28Left shift security in our workflowPhilippe Lafoucrière
2018-11-27Clearer docs when it is OK for maintainer to squashDylan Griffith