summaryrefslogtreecommitdiff
path: root/danger/prettier
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-03-121-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-111-1/+1
|
* Add new GitlabDanger classAsh McKenzie2019-09-061-12/+14
| | | | 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-061-14/+12
| | | This reverts merge request !32196
* Update some Danger rules to not rely upon CI66596-allow-danger-to-be-run-locallyAsh McKenzie2019-09-061-12/+14
| | | | | Convert a bunch of Danger rules so they can run locally.
* Create helper to get all changed filesleipert-danger-fix-moved-filesLukas Eipert2018-10-221-1/+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 unprettified JavaScriptLukas Eipert2018-09-281-0/+39
This adds a Dangerfile which executes `prettier` to find out if someone touched Frontend files and forgot to run it on their current branch.