-
Notifications
You must be signed in to change notification settings - Fork 0
Issue Submission Guide
GitLab is developed by a small core team of developers who like to spend their time making GitLab a better product for you. If you open a new issue in the issue tracker, please be patient as we may not be able to respond to it immediately. But don't worry, we read them all and we will work hard to get in touch with you or to fix them as soon as possible.
Some errors are common and it may so happen, that you are not the only one who stumbled over a particular issue. We have collected several of those and documented quick solutions for them.
In order:
When you encounter an issue with GitlabHQ, first consider what kind of issue you have. If it's an obvious bug or feature request, post it in Github Issues. All other issues should be discussed on the Mailinglist first.
- You get permission denied errors
- You can't see your repos
- You have issues cloning, pulling or pushing
- You have issues with web_hooks not firing
Use The Search before posting, there's a good chance somebody else had the same issue you did.
- You found an obvious bug
- Have a feature request
If you're unsure where to post, post it to the mailinglist. There are a lot of helpful GitlabHQ users there who may be able to help you quickly.
If your issue is a bug it will find its way from the mailinglist to Github Issues.
By posting your question or issue to the proper location, you allow the development team to focus on development of GitlabHQ (including fixing bugs).
Please use the following outline for new issue submissions
By taking the time to ask your question in the right place, you give the development team more time to develop GitLab into a better product for us all.