-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
move pre-commit hook back to travis #3195
Conversation
Ok, I had not yet discovered "Show full screen". But this is still no solution for the phone, where it switches back to desktop view. Also all the hide buttons are still annoying. The Travis experience is much more pleasant compared to that. For my understanding we have switched to GitHub for an improved user experience, but the opposite is the case. What is the drawback to just switch back? |
The Full screen button works on my phone.
I actually like them a lot, because that way I don't need to scroll down so much and my phone doesn't slow down due to hundres/thousands of lines.
I see your points, and the experience is not perfect. But I still like it a lot better than Travis, which has problems of its own. Slowdowns due to log loading (in contrast to lazy loading on GH Actions) and the non-working back buttons is quite annoying.
One of the reasons was visibility to first-time contributors, yes. But I also proposed the switch to clear up the Travis Build queue, so that pre-commit jobs don't block build jobs and increases the waiting time. |
@mixxxdj/continuous-integration-managers What do the others think? |
Idea: I could also look into checking the output, and write a bot thwt comments on the PR if the pre-commit hook fails. That comment could explain how to install/use the precommit hooks and a link to a gist with the patch diff and how to apply that diff using |
Did you see a mobile view? I can also switch to full screen but the text is not readable without a magnifier glass. I use Chrome on Android.
This is not the case on Travis for the pre-commit hook. It also hides relevant lines and reduces the output from 1378 to 80 lines. You other points are valid for me, I suffer the missing back button as well. Unfortunately this does not outweigh the usability shortcomings here. |
This has been discussed here: |
Ah, I didn't notice how small it is because I usually turn my phone sideways to read code. This is how it looks for me: |
Unfortunately only the 6 lines are scrolled. The whole website is not scroll-able. |
If you like to go this extra mile? |
I disagree. The full-screen view works well, why should we go back to Travis? The pre-commit hook is supposed to be executed locally by developers before publishing a PR. The GitHub Action is only the final quality gate and not intended as a development tool. |
What environment do you use? The issue is that new contributors will likely have the pre-commit hook not installed. This is the only case where the hook ever fails. For these users and for the reviewers we nee a smooth experience. I think I have reasonable outlined that the full-screen view does not work well and is hard to discover. This applies especially to new contributors. I will ask on Zulip. |
Converted to draft, because we don't have an agreement yet. |
I will close this sind my opinion seems to be a minority. |
Unfortunately the output of the pre-commit hook on GitHub is only usable on BIG screens.
Travis did a good job in the past, so let's move back until we have a solution on GitHub.