You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
The services hooks page is a really really long list with no sorting, no searching, and a very small font. As of writing this there are 140 items in this list.
The flow to use it is really bad too. For example, if I want to add travis-ci to a repo:
First I have to find the travis-ci link in this huge list
Then I select it, scroll all the way back up, enter my key, and press save. I get a full page refresh which clears the currently select service hook. Now I want to test the hook so I repeat the same process and find this tiny "Travis" link and click it. Click test hook.
Process completed!
Suggestions:
Show active service hooks with a green indicator right at the top of the list
Make the font bigger on that list
Add on-page searching of the list
Don't do a full refresh when you add a service hook.
If you have to do a full refresh, maybe have a "Save and Test" button?
When you write like 5 npm modules a day and you have to repeat this process each time it will get under your skin. Sorry for the rant.
The text was updated successfully, but these errors were encountered:
The services hooks page is a really really long list with no sorting, no searching, and a very small font. As of writing this there are 140 items in this list.
The flow to use it is really bad too. For example, if I want to add travis-ci to a repo:
First I have to find the travis-ci link in this huge list
Then I select it, scroll all the way back up, enter my key, and press save. I get a full page refresh which clears the currently select service hook. Now I want to test the hook so I repeat the same process and find this tiny "Travis" link and click it. Click test hook.
Process completed!
Suggestions:
When you write like 5 npm modules a day and you have to repeat this process each time it will get under your skin. Sorry for the rant.
The text was updated successfully, but these errors were encountered: