gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2021-03-31	Add latest changes from gitlab-org/security/gitlab@13-10-stable-ee	GitLab Bot

2021-01-20	Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42	Robert Speicher

2020-12-17	Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42	GitLab Bot

2020-08-20	Add latest changes from gitlab-org/gitlab@13-3-stable-ee	GitLab Bot

2020-07-20	Add latest changes from gitlab-org/gitlab@13-2-stable-ee	GitLab Bot

2020-03-05	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-03-02	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-02-07	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-10-23	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-08-22	Add frozen_string_literal to lib part 2	Thong Kuah
	Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2018-07-11	Resolve "Rename the `Master` role to `Maintainer`" Backend	Mark Chao

2018-06-01	Rephrase "maintainer" to more precise "members who can merge to the target ↵	Mark Chao
	branch" "Maintainer" will be freed to be used for #42751
2018-04-24	Allow admins to push to empty repos	Bob Van Landuyt

2018-03-07	Allow maintainers to push to a single branch	Bob Van Landuyt

2017-12-22	Replace '.team << [user, role]' with 'add_role(user)' in specs	blackst0ne

2017-08-01	Ensure all project factories use `:repository` trait or `:empty_project`	Robert Speicher

2017-07-27	Use described_class when possible	Rémy Coutable
	Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-07-27	Remove superfluous lib: true, type: redis, service: true, models: true, ↵	Rémy Coutable
	services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-05-08	Add confirm delete protected branch modal	Sam Rose

2017-04-28	Prevent people from creating branches if they don't have persmission to push	Pawel Chojnacki

2017-04-04	Renamed ProtectedTag push_access_levels to create_access_levels	James Edwards-Jones

2017-04-04	Cleaned up duplication with ProtectedRefAccess concern	James Edwards-Jones

2017-04-04	Cleanup & tests for UserAccess#can_create_tag?	James Edwards-Jones

2017-01-13	Allow creating protected branch when it doesn't exist	Pawel Chojnacki
	if user has either push or merge permissions + Change log entry for fix to creating a branch matching a wildcard fails
2016-08-04	changes default_branch_protection to allow devs_can_merge protection option ↵	tiagonbotelho
	aswell
2016-08-02	developer cannot push to protected branch when project is empty or he has ↵	tiagonbotelho
	not been granted permission to do so
2016-07-29	Enforce "No One Can Push" during git operations.	Timothy Andrew
	1. The crux of this change is in `UserAccess`, which looks through all the access levels, asking each if the user has access to push/merge for the current project. 2. Update the `protected_branches` factory to create access levels as necessary. 3. Fix and augment `user_access` and `git_access` specs.
2016-07-18	Revert "Revert "Merge branch '18193-developers-can-merge' into 'master' ""	Rémy Coutable
	This reverts commit 530f5158e297f3cde27f3566cfe13bad74ba3b50. See !4892. Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-07-13	Revert "Merge branch '18193-developers-can-merge' into 'master' "	Robert Speicher
	This reverts commit 9ca633eb4c62231e4ddff5466c723cf8e2bdb25d, reversing changes made to fb229bbf7970ba908962b837b270adf56f14098f.
2016-07-13	Implement last round of review comments from !4892.	Timothy Andrew
	1. Fix typos, minor styling errors. 2. Use single quotes rather than double quotes in `user_access_spec`. 3. Test formatting.
2016-07-13	Refactor `Gitlab::GitAccess`	Timothy Andrew
	1. Don't use case statements for dispatch anymore. This leads to a lot of duplication, and makes the logic harder to follow. 2. Remove duplicated logic. - For example, the `can_push_to_branch?` exists, but we also have a different way of checking the same condition within `change_access_check`. - This kind of duplication is removed, and the `can_push_to_branch?` method is used in both places. 3. Move checks returning true/false to `UserAccess`. - All public methods in `GitAccess` now return an instance of `GitAccessStatus`. Previously, some methods would return true/false as well, which was confusing. - It makes sense for these kinds of checks to be at the level of a user, so the `UserAccess` class was repurposed for this. The prior `UserAccess.allowed?` classmethod is converted into an instance method. - All external uses of these checks have been migrated to use the `UserAccess` class 4. Move the "change_access_check" into a separate class. - Create the `GitAccess::ChangeAccessCheck` class to run these checks, which are quite substantial. - `ChangeAccessCheck` returns an instance of `GitAccessStatus` as well. 5. Break out the boolean logic in `ChangeAccessCheck` into `if/else` chains - this seems more readable. 6. I can understand that this might look like overkill for !4892, but I think this is a good opportunity to clean it up. - http://martinfowler.com/bliki/OpportunisticRefactoring.html