summaryrefslogtreecommitdiff
path: root/Dangerfile
Commit message (Collapse)AuthorAgeFilesLines
* Add Danger rule for EE/CE templatesNathan Friend2019-04-241-0/+2
| | | | | | This commit adds a rule to Danger that warns the developer when their MR includes changes to a CE .vue file that has a counterpart in the EE repo or vice-versa.
* Exempt release automation MRs from Danger rulesRobert Speicher2019-04-041-15/+18
|
* Set specific reviewers for the GitLab UI WG effortgl-set-up-gitlab-ui-danger-reviewerFilipa Lacerda2019-03-291-0/+1
|
* Set specific reviewers for single codebase effortMarin Jankovski2019-03-111-0/+1
| | | | | | | This extends Danger so it informs MR authors that single codebase merge requests need to be approved by a specific group of engineers. Co-authored-by: Yorick Peterse <yorickpeterse@gmail.com>
* Reviewer roulette via Danger56087-danger-rouletteNick Thomas2019-02-131-0/+1
| | | | | | Make danger pick reviewers and maintainers at random, for feontend, backend, database, etc, changes, whenever files belonging to those teams get changed.
* Add danger check for duplicate yarn dependenciesLukas Eipert2018-12-171-0/+1
| | | | | | | | | | | | This danger check utilises `yarn-deduplicate` in order to show duplicate dependencies in the yarn.lock dependency tree. Often when introducing new dependencies or updating existing ones, yarn does not seem to build the most optimal dependency tree. In order to prevent those unnecessary dependency updates we are nudging developers and maintainers to resolve these issues in MRs. Automating this with danger especially helps, as yarn.lock files are not that easy to review.
* Create helper to get all changed filesleipert-danger-fix-moved-filesLukas Eipert2018-10-221-0/+1
| | | | | | | | | | | | | | | | Danger apparently has three different objects which could contain files you often want to check: - git.added_files - git.modified_files - git.renamed_files The problem: If a file is renamed, `modified_files` contains the file path before the rename. In some Danger checks we use `added_files` + `modified_files`, which might contain the deleted paths of renamed files, but missing the new paths of renamed files. So we need to consider `renamed_files` as well.
* Danger check for ignored eslint rulesleipert-frontend-dangerLukas Eipert2018-09-291-0/+1
| | | | | | We disabled a lot of eslint rules on a per-file basis. This checks touched files for those and reminds you to re-enable the rules and fix them.
* Danger check for unprettified JavaScriptLukas Eipert2018-09-281-0/+1
| | | | | This adds a Dangerfile which executes `prettier` to find out if someone touched Frontend files and forgot to run it on their current branch.
* Added Danger file to lint commit messagesYorick Peterse2018-09-101-0/+1
| | | | | | | | | | | | | | | | This Dangerfile ensures that commit authors write good commit messages. We also prevent the use of Emoji, since these add no value and may not always be displayed properly. Merge commits are currently ignored. In the future we most likely want to stop using these, but this is a separate discussion, hence we ignore them for the time being. The rules enforced by this Dangerfile are based on the article found at https://chris.beams.io/posts/git-commit/. For more information, refer to https://gitlab.com/gitlab-org/gitlab-ce/issues/50003. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/50003
* Add Documentation DangerfileAchilleas Pipinellis2018-09-061-0/+1
| | | | | Every time a doc change is made, a comment to ping the @gl-docsteam is added.
* Add Dangerfile for frozen_string_literalgfyoung2018-07-241-0/+1
| | | | | | | Checks that new Ruby files will enable frozen string literal. Partially addresses #47424.
* Start to use Danger for automating MR reviewsRémy Coutable2018-07-111-0/+6
Signed-off-by: Rémy Coutable <remy@rymai.me>