[nfbcs] Software Version Control with Gitlab v9.3.5

[John Miller]

Hello,
I am looking to hear from other blind software developers about their experience working with a Gitlab server which provides software version control.
If you have access to a Linux machine, would you be willing to host a Gitlab server on it and allow 1 or 2 developers to have an account on the server so that we can explore how to make it more accessible?

At work I am using Git and Gitlab for software version control.
The company Gitlab www.gitlab.com<http://www.gitlab.com> provides a server on which a company can store software projects.
A person interacts with the server via a web interface.
I have been using JAWS 16 and Internet Explorer.
Gitlab has a note on their website indicating that a bug has been created about blindness access.
I am comfortable using Git from the Linux command line to clone a repository, checkout a file, commit changes, push changes to a remote repository, and switch between branches.

One of the things you can do on the Gitlab server is create a new issue (a bug or feature) for your favorite project.
The tab order on the Gitlab web page does not seem correct.
At one point I had to tab 15 times to land on the new issue link for my project of interest.
Two other activities you can do on the Gitlab server are create a branch from an issue and initiate a merge request to the master branch for a branch.
Without sighted assistance I could not figure out how to create a branch from an issue.
It would be helpful to hear from others about the steps to independently create a branch from an issue or create a merge request for a branch.
One thing I have learned how to do is the use the Gitlab API in order to get a list of issues and projects sent to my local machine from the Gitlab server. There may be command line tools that work with Gitlab to meet the needs I described.
Please contact me on the list or at johnmillerphd at hotmail.com<mailto:johnmillerphd at hotmail.com>.
Thank you for your help.
very best,
John Miller