-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update GitDone for new GitHub UI #18
Comments
@darrenmothersele Hi, Darren. The new interface is actually much improved -- and actually makes our job much easier, in terms of simplifying the interface for Task Masters. New proposed GitDone interfaceHere's a mock-up of what we'll want to do now: 1) Issues pageand... that's it! This eliminates a lot of clutter and confusion for people who never touch code. 2) Code pageThat's it! |
I cleaned up this ticket to make it clearer. Implementing the two mock-ups above are enough to start testing. |
@OpenMatt - I added the code to make these changes. I've left in most of the previous code, I noticed the old UI was still in effect in places when I was logged out of GitHub. I also added an edit button for the project readme on the repo home page, and simplified the readme edit screen a bit. I've removed |
@darrenmothersele amazing! thanks I'll try it out. :) |
Latest news is that GitHub repos are getting a new look.
https://github.com/blog/2085-a-new-look-for-repositories
At MozFest we spoke about the fragility of coding against unpublished details of the structure of GitHub's markup.
I'm not sure yet how much the new GitHub repo design will affect the UI rewriting we are doing.
Perhaps some kind of visual regression testing bot to catch when things break?
It looks like it could be possible with Travis CI
https://travis-ci.org/
https://twolfson.com/2014-02-25-visual-regression-testing-in-travis-ci
The text was updated successfully, but these errors were encountered: