- Mar 23, 2020
-
-
GitLab Bot authored
-
- Feb 27, 2020
-
-
GitLab Bot authored
-
- Feb 06, 2020
-
-
GitLab Bot authored
-
- Jan 30, 2020
-
-
GitLab Bot authored
-
- Nov 21, 2019
-
-
GitLab Bot authored
-
- Nov 11, 2019
-
-
GitLab Bot authored
-
- Nov 05, 2019
-
-
GitLab Bot authored
-
- Oct 27, 2019
-
-
GitLab Bot authored
-
- Oct 11, 2019
-
-
GitLab Bot authored
-
- Sep 27, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Aug 27, 2019
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Aug 13, 2019
-
-
- 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
-
- Jul 19, 2019
- Jul 15, 2019
-
-
- Jul 04, 2019
-
-
Marin Jankovski 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
-
- Jun 25, 2019
-
-
Also adds and one linting rule and makes project conform to it.
-
- May 05, 2019
-
-
- Mar 13, 2019
-
-
Marcel Amirault authored
-
- Mar 05, 2019
-
-
Marcel Amirault authored
-
- Feb 11, 2019
-
-
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).
-
- Feb 06, 2019
-
-
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.
-
- Jan 24, 2019
-
-
- Dec 24, 2018
-
-
Jacob Wolen authored
-
- Nov 02, 2018
-
-
Sanad Liaquat authored
-
- Nov 01, 2018
-
-
Sanad Liaquat authored
-
- Oct 29, 2018
-
-
Sanad Liaquat authored
-
- Oct 22, 2018
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Oct 11, 2018
-
-
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>
-
- Oct 09, 2018
-
-
Dimitrie Hoekstra authored
-
- Sep 27, 2018
-
-
Evan Read authored
- Also fix some markdown syntax.
-
- Sep 06, 2018
-
-
Brett Walker authored
-
- Aug 09, 2018
-
-
Eddie Stubbington authored
-