To prevent password probing, accounts should be locked after a number of failed attempts (login screen and via GIT itself) or at least further attempts should be delayed.1 vote
By default GitLab has rate limiting enabled https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/security/rack_attack.md
There should be an option in gitlab.yml for usage of Piwik as there already is for Google Analytics.1 vote
Implemented in GitLab 6.7
Would be great to have the option to set master branch protected by default when creating a new project.
I have to do it manually everytime7 votes
In GitLab 7.4
For unassigned issues in GitLab Issues, developers should be able to assign them to themselves to "pick up" the issues.117 votes
In GitLab 6.6
Right now snippets are called private and public but the behavior is like private and internal (user with accounts can view them only). Existing snippets should become internal and a new real public mode should be introduced. This functionality should respect the public/internal setting in gitlab.yml56 votes
In GitLab 7.4
We're currently using https://github.com/git-commit-notifier/git-commit-notifier for this.
It can be tacked on via webhooks, but it would be nice to have this built-in and available for both code and wiki repos.18 votes
You can get nice html diffs via the email-on-push service.
It currently shows: let's hide it in that case.1 vote
In GitLab 7.4
This is currently not possible with omnibus-gitlab. The implementation is sketched in https://gitlab.com/gitlab-org/omnibus-gitlab/issues/124#note_102379 .7 votes
Implemented in 7.1 with https://gitlab.com/gitlab-org/omnibus-gitlab/commit/b5f19500a09c3244a35b91dcccd45dacbfd93010
It would be nice to have Task lists implementation for isssues like github done (https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments) or some other implementation of subtasks.292 votes
Contributed to GitLab 7.4 in https://github.com/gitlabhq/gitlabhq/pull/7964
Allow referencing issues and merge requests from different repos.
The GitHub markdown for this is "user/repository#number" - a similar markdown can be used here.79 votes
Contributed in GitLab 7.4 in https://github.com/gitlabhq/gitlabhq/pull/7933
It would be nice to be able to filter the issues via the API based on its state (open|closed) and the tags.
So you could scope on one state and maybe multiple tags.3 votes
Shipped with GitLab 7.3
Add functionality to the api so that only opened or reopened issues can be get.9 votes
Shipped with GitLab 7.3
There is currently not any API call for normal users to use to fork a project. That is: if Alice wants to fork `bob/project` she must go to the website.
The API allows an admin to take a non-fork `alice/project` and mark it as a fork of `bob/project`, but this should not be required.
I believe that this is actually what http://feedback.gitlab.com/forums/176466-general/suggestions/4125380-to-be-able-to-fork-a-project-through-the-api was requesting.22 votes
Implemented and all be available in GitLab 7.4
Will be available in GitLab 7.4
It would be nice to have an option for storing the local backups on a remote server. For example :
1. Amazon S3
2. Google Drive
4. SFTP on some remote machine419 votes
In GitLab 7.4 a backup uploader with fog (also supports s3) is included. Merged in https://gitlab.com/gitlab-org/gitlab-ce/commit/9654cbb5924c968cdefcb83732b313c54fe292d1. Documentation is at http://doc.gitlab.com/ce/raketasks/backup_restore.html under “Upload backups to remote (cloud) storage”
Add commit message to Email on Push subject instead of the static "New push to repository".
If multiple commits – change subject to message like this: "N new commits".4 votes
In GitLab since 7.0.
Sometimes instead of adding few team members, you want to add everybody to the notification (CC) list of an issue. There should be a better way of adding everyone to notification list other than mentioning everybody with @ tags by their names at the end of an comment.
I'm thinking that maybe the name of the Group or project can be used for that purpose. e.g. @ProjectName or @GroupName would have gotten everybody notified...?4 votes
In GitLab 7.1 you can use @all to mention all project members.
I have a use case where I need to have a project be public for the sake of only reporting issues on that project, thus any person who is able to register an account would be able to view the projects issues and submit new ones - only. No code pulling, no code viewing, no snippets, etc. Just issues.
Any way we could get this done? The guest access already exists, but it includes code access, which I can't have.
Guest access should not include access to code, only:
Create new issue
Write on project wall
I currently use Redmine for my issues in oreder to do time-tracking, gantt, versions, guest access. I think it would be cool to allow setup for Redmine issues to be synced into Gitlab and possibly vice versa.35 votes
You can now link Redmine issues from GitLab https://github.com/gitlabhq/gitlabhq/blob/089605fe6b9850ff87e1b1535d084b73e305d627/config/gitlab.yml.example#L54
- Don't see your idea?