summaryrefslogtreecommitdiff
path: root/danger
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-281-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-271-51/+22
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-271-4/+18
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-241-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-231-12/+22
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-221-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-171-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-161-1/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-091-0/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-051-0/+19
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-031-0/+50
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-261-36/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-142-66/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-121-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-031-0/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-162-231/+102
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-042-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-261-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-201-10/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-122-28/+16
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-111-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-101-3/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-281-1/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-273-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-261-4/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-181-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-151-1/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-041-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-231-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-184-5/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-172-24/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-161-2/+8
|
* Danger: Allow fixup commits if squash enabled or MR is WIPElan Ruusamäe2019-09-101-1/+28
|
* Add new GitlabDanger classAsh McKenzie2019-09-067-55/+88
| | | | This class encapsulates our use of the Danger gem.
* Revert "Merge branch '66596-allow-danger-to-be-run-locally' into 'master'"revert-351d72cbAsh McKenzie2019-09-067-88/+55
| | | This reverts merge request !32196
* Update some Danger rules to not rely upon CI66596-allow-danger-to-be-run-locallyAsh McKenzie2019-09-067-55/+88
| | | | | Convert a bunch of Danger rules so they can run locally.
* Change docs markdown linterMarcel Amirault2019-08-261-1/+1
| | | | | | | Change from ruby mdl to node markdownlint, add config file to root of project, delete old config file, update exceptions, and fix one doc that was didn't meet standards
* Make it clear that it's ok to ignore Danger's 'no changelog' warningimprove-dnager-message-when-changelog-is-neededRémy Coutable2019-08-221-7/+6
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Make Danger consider .md files as documentation filesconsider-md-files-as-doc-in-danger-checkRémy Coutable2019-08-211-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix duplicated suggestion in Danger gem warningfix-danger-gemfile-warningTiger2019-07-241-2/+1
|
* Document database review processToon Claes2019-07-192-29/+28
| | | | See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
* Merge branch 'danger-throughputs' into 'master'Lin Jen-Shin2019-07-171-0/+12
|\ | | | | | | | | Danger asks for throughput labels See merge request gitlab-org/gitlab-ce!30622
| * Danger asks for throughput labelsdanger-throughputsMark Fletcher2019-07-111-0/+12
| |
* | Do not fail danger if suggestion commit msg > 72Achilleas Pipinellis2019-07-161-10/+13
|/ | | | | | | We have another rule that requires squash enabled when suggestions are applied. No need to fail the ones that are more than 72 characters long since they will be squashed anyway.
* Docs: Update danger to accept docs linting changesMarcel Amirault2019-07-091-1/+1
|
* Update dangerfile to exclude docs ci yamlMarcel Amirault2019-07-061-1/+1
|
* DRY up conditions for files require DB reviewToon Claes2019-07-041-31/+1
| | | | | | | | Stop using two separate lists for the conditions which files require a database review. Related discussion: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30156#note_187732053
* Add a danger rule to suggest `docs-` prefixesleipert-danger-dogsLukas Eipert2019-06-271-0/+24
| | | | | | | | | | If an MR only changes files within `doc/` we can save valueable CI time by prepending a branch name with `docs-`. This danger rule helps educate people about that fact. On the other hand, if someone has a branch with a `docs` prefix or suffix, the branch shouldn't contain any changes outside of the `docs` directory
* When using suggestions, squash must be enabledAchilleas Pipinellis2019-06-191-1/+11
|
* Backport the EE schema and migrations to CEYorick Peterse2019-06-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This backports all EE schema changes to CE, including EE migrations, ensuring both use the same schema. == Updated tests A spec related to ghost and support bot users had to be modified to make it pass. The spec in question assumes that the "support_bot" column exists when defining the spec. In the single codebase setup this is not the case, as the column is backported in a later migration. Any attempt to use a different schema version or use of "around" blocks to conditionally disable specs won't help, as reverting the backport migration would also drop the "support_bot" column. Removing the "support_bot" tests entirely appears to be the only solution. We also need to update some foreign key tests now that we have backported the EE columns. Fortunately, these changes are very minor. == Backporting migrations This commit moves EE specific migrations (except those for the Geo tracking database) and related files to CE, and also removes any traces of the ee/db directory. Some migrations had to be modified or removed, as they no longer work with the schema being backported. These migrations were all quite old, so we opted for removing them where modifying them would take too much time and effort. Some old migrations were modified in EE, while also existing in CE. In these cases we took the EE code, and in one case removed them entirely. It's not worth spending time trying to merge these changes somehow as we plan to remove old migrations around the release of 12.0, see https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
View Lorry Controller Status