| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | 2020-06-18 | 1 | -2/+8 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | 2020-05-20 | 1 | -0/+44 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-27 | 1 | -3/+3 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-30 | 1 | -2/+2 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 1 | -1/+1 |
| | | |||||
| * | Update capitalization in admin, api, others | Marcel Amirault | 2019-08-23 | 1 | -2/+2 |
| | | | | | | Update capitalization in /administration, /api, /ci and /customization | ||||
| * | Allow setting feature flags per GitLab group | James Edwards-Jones | 2019-02-19 | 1 | -1/+2 |
| | | | | | | | | | Building on support for setting feature flags by project, this adds support for setting them by GitLab group path. This is different from setting them by Flipper feature_groups, which are for batch updating pre-registered collections. | ||||
| * | Allow setting of feature gates per project | Zeger-Jan van de Weg | 2019-01-14 | 1 | -2/+3 |
| | | | | | | | | | | For features the feature gates are sometimes projects, not groups or users. For example for git object pools: https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/5872 This commit allows for setting feature group gates based on projects, by its path as that seems most convenient. | ||||
| * | Replace look-alike token with '<your_access_token>'docs/fake-token-no-more | Achilleas Pipinellis | 2019-01-04 | 1 | -2/+2 |
| | | | | | | Replace all '9koXpg98eAheJpvBs5tK' occurrences with '<your_access_token>' in API docs. | ||||
| * | Allow feature gate removal through the APIzj-feature-gate-remove-http-api | Zeger-Jan van de Weg | 2018-04-03 | 1 | -0/+8 |
| | | | | | | | Features could be listed and added through the api, now also removed. This was needed in the case of gitlab.com as the number of gates that were ever used just grows and cleaning up is hard. | ||||
| * | Improve Features API and its docs and add a Changelog item | Rémy Coutable | 2017-07-06 | 1 | -2/+2 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Document the feature groups | Rémy Coutable | 2017-07-06 | 1 | -1/+1 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Address #34528 by improving the feature flags documentation | Rémy Coutable | 2017-07-06 | 1 | -1/+2 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Rename flipper_group to feature_group34078-allow-to-enable-feature-flags-with-more-granularity | Rémy Coutable | 2017-06-28 | 1 | -2/+2 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Rename FLippable to FeatureGate and make `flipper_group` and `user` mutually ↵ | Rémy Coutable | 2017-06-27 | 1 | -0/+2 |
| | | | | | | | exclusive Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Allow the feature flags to be enabled/disabled with more granularity | Rémy Coutable | 2017-06-27 | 1 | -0/+2 |
| | | | | | | | | | This allows to enable/disable a feature flag for a given user, or a given Flipper group (must be declared statically in the `flipper.rb` initializer beforehand). Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Add feature toggles through Flipper | Alejandro Rodríguez | 2017-05-31 | 1 | -0/+83 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |