Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-17 | 1 | -4/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-16 | 1 | -1/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-09 | 1 | -0/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-05 | 1 | -0/+19 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-03 | 1 | -0/+50 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-26 | 1 | -36/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-14 | 2 | -66/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-12 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-03 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-16 | 2 | -231/+102 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-04 | 2 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-26 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-20 | 1 | -10/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-12 | 2 | -28/+16 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-11 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-10 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-28 | 1 | -1/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-27 | 3 | -4/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-26 | 1 | -4/+6 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-18 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-15 | 1 | -1/+7 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-04 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-23 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 4 | -5/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-17 | 2 | -24/+6 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-16 | 1 | -2/+8 |
| | |||||
* | Danger: Allow fixup commits if squash enabled or MR is WIP | Elan Ruusamäe | 2019-09-10 | 1 | -1/+28 |
| | |||||
* | Add new GitlabDanger class | Ash McKenzie | 2019-09-06 | 7 | -55/+88 |
| | | | | This class encapsulates our use of the Danger gem. | ||||
* | Revert "Merge branch '66596-allow-danger-to-be-run-locally' into 'master'"revert-351d72cb | Ash McKenzie | 2019-09-06 | 7 | -88/+55 |
| | | | This reverts merge request !32196 | ||||
* | Update some Danger rules to not rely upon CI66596-allow-danger-to-be-run-locally | Ash McKenzie | 2019-09-06 | 7 | -55/+88 |
| | | | | | Convert a bunch of Danger rules so they can run locally. | ||||
* | Change docs markdown linter | Marcel Amirault | 2019-08-26 | 1 | -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-needed | Rémy Coutable | 2019-08-22 | 1 | -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-check | Rémy Coutable | 2019-08-21 | 1 | -1/+1 |
| | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
* | Fix duplicated suggestion in Danger gem warningfix-danger-gemfile-warning | Tiger | 2019-07-24 | 1 | -2/+1 |
| | |||||
* | Document database review process | Toon Claes | 2019-07-19 | 2 | -29/+28 |
| | | | | See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069 | ||||
* | Merge branch 'danger-throughputs' into 'master' | Lin Jen-Shin | 2019-07-17 | 1 | -0/+12 |
|\ | | | | | | | | | Danger asks for throughput labels See merge request gitlab-org/gitlab-ce!30622 | ||||
| * | Danger asks for throughput labelsdanger-throughputs | Mark Fletcher | 2019-07-11 | 1 | -0/+12 |
| | | |||||
* | | Do not fail danger if suggestion commit msg > 72 | Achilleas Pipinellis | 2019-07-16 | 1 | -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 changes | Marcel Amirault | 2019-07-09 | 1 | -1/+1 |
| | |||||
* | Update dangerfile to exclude docs ci yaml | Marcel Amirault | 2019-07-06 | 1 | -1/+1 |
| | |||||
* | DRY up conditions for files require DB review | Toon Claes | 2019-07-04 | 1 | -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-dogs | Lukas Eipert | 2019-06-27 | 1 | -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 enabled | Achilleas Pipinellis | 2019-06-19 | 1 | -1/+11 |
| | |||||
* | Backport the EE schema and migrations to CE | Yorick Peterse | 2019-06-17 | 1 | -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. | ||||
* | Excludes MR author from Review roulette61157-reviewer-roulette-shouldn-t-include-the-author-as-a-possibility | Jacopo | 2019-06-12 | 3 | -22/+29 |
| | | | | | Excludes MR author from gitlab_ui and single_codebase Review roulette results. | ||||
* | Don't fail the pipeline when a colon-emoji is used | Sean McGivern | 2019-06-06 | 1 | -2/+2 |
| | | | | | | A colon-emoji like :100: can be valid in the case where we're talking about the GitLab feature that processes these into emojis. It's fine to warn about those, but failing the pipeline is too restrictive. | ||||
* | Show Test Automation Engineer for spec/feature as | Lin Jen-Shin | 2019-06-06 | 1 | -3/+7 |
| | | | | reviewers. | ||||
* | Use roulette for single codebase rouletteextract-danger-roulette | Lin Jen-Shin | 2019-05-30 | 1 | -11/+18 |
| | |||||
* | Extract roulette to its own module | Lin Jen-Shin | 2019-05-30 | 3 | -42/+16 |
| | | | | So it's more modular and extensible | ||||
* | Run rubocop -a on CE filessh-upgrade-rubocop-0.68.0-ce | Stan Hu | 2019-05-05 | 1 | -1/+1 |
| |