An error occurred fetching the project authors.
- 27 Feb, 2020 1 commit
-
-
GitLab Bot authored
-
- 06 Feb, 2020 1 commit
-
-
GitLab Bot authored
-
- 30 Jan, 2020 1 commit
-
-
GitLab Bot authored
-
- 21 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 11 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 05 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 27 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 11 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 27 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 18 Sep, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 27 Aug, 2019 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 13 Aug, 2019 1 commit
-
-
Doug Stull authored
- 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
-
- 19 Jul, 2019 1 commit
-
-
- 15 Jul, 2019 1 commit
-
-
Michel Engelen authored
-
- 04 Jul, 2019 2 commits
-
-
Marin Jankovski authored
-
Marcel Amirault authored
After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting
-
- 25 Jun, 2019 1 commit
-
-
Evan Read authored
Also adds and one linting rule and makes project conform to it.
-
- 05 May, 2019 1 commit
-
-
Marcel Amirault authored
-
- 13 Mar, 2019 1 commit
-
-
Marcel Amirault authored
-
- 05 Mar, 2019 1 commit
-
-
Marcel Amirault authored
-
- 11 Feb, 2019 1 commit
-
-
Yorick Peterse authored
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).
-
- 06 Feb, 2019 1 commit
-
-
Yorick Peterse authored
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.
-
- 24 Jan, 2019 1 commit
-
-
Evan Read authored
-
- 24 Dec, 2018 1 commit
-
-
Jacob Wolen authored
-
- 02 Nov, 2018 1 commit
-
-
Sanad Liaquat authored
-
- 01 Nov, 2018 1 commit
-
-
Sanad Liaquat authored
-
- 29 Oct, 2018 1 commit
-
-
Sanad Liaquat authored
-
- 22 Oct, 2018 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 11 Oct, 2018 1 commit
-
-
Rémy Coutable authored
This removes duplicated content from CONTRIBUTING.md and consolidate everything under doc/development/contributing/. This also fixes missing links. Lastly, this moves the style guides from the "Implement design & UI elements" page to a new "Style guides" page. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 09 Oct, 2018 1 commit
-
-
Dimitrie Hoekstra authored
-
- 27 Sep, 2018 1 commit
-
-
Evan Read authored
- Also fix some markdown syntax.
-
- 06 Sep, 2018 1 commit
-
-
Brett Walker authored
-
- 09 Aug, 2018 1 commit
-
-
Eddie Stubbington authored
-