-
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.
Please visit our Support Forum for any kind of question regarding the usage or adiministration/configuration of GitLab.
- 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
Search for similar issues before posting your own, there's a good chance somebody else had the same issue you have now and had it resolved.
- You found an obvious bug or misbehavior in GitLab
- You found pieces of documentation problematic or insufficient
- Have a feature suggestion
If you're unsure where to post, post it to the Support Forum first. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there to the issue tracker on GitHub.
Search for similar entries before submitting your own, there's a good chance somebody else had the same issue or idea. Show your support with :+1: and/or join the discussion.
Please consider the following points when submitting an issue:
- Summarize your issue in one sentence (what happened wrong, when you did/expected something else)
- Describe your issue in detail (including steps to reproduce)
- Add logs or screen shots when possible
- Describe your setup (use relevant parts from
sudo -u gitlab -H bundle exec rake gitlab:env:info)
Please consider the following points when submitting a feature suggestion:
- Summarize your suggestion in one sentence
- Describe your idea (intent, use cases, benefits, caveats, mock ups, etc.)
- Where appropriate, provide comparisons to other solutions
- Can it be broken down into smaller parts?
- Would you be willing to implement it?
By taking the time to ask your question in the right place, you help the development team to organize and prioritize issues and suggestions in order to make GitLab a better product for us all.