HackerTrans
TopNewTrendsCommentsPastAskShowJobs

gimenete

no profile record

Submissions

Show HN: GitSwipe, Inbox zero for GitHub notifications

gitswipe.com
1 points·by gimenete·5 bulan yang lalu·0 comments

comments

gimenete
·6 bulan yang lalu·discuss
https://gitswipe.com/

A mobile app for triaging GitHub notifications in seconds. Available for iOS and Android starting next week.
gimenete
·9 bulan yang lalu·discuss
Electron was originally named Atom Shell https://www.electronjs.org/blog/electron/

Atom Shell/Electron was from the very beginning something you could use separately from Atom as a framework for creating desktop apps using Chromium/Node.js.
gimenete
·11 bulan yang lalu·discuss
This is not an alternative to GitHub but an alternative frontend. The backend is still GitHub.
gimenete
·11 bulan yang lalu·discuss
My main goal is to offer a more modern and smoother experience than GitHub, add some features on top of it like push notifications, triage of notifications, a better editing experience,… and integrate the desktop app with your local git
gimenete
·11 bulan yang lalu·discuss
Thanks!

Good question. I don't have now right now but I can prepare one soon. In any case I store zero information from users. When you are logged in traffic goes directly from your browser to GitHub.
gimenete
·11 bulan yang lalu·discuss
I don't remember clearly where we moved them. It was probably to something owned by Google (because GitHub uses Google Workspaces) or Microsoft (for obvious reasons).
gimenete
·11 bulan yang lalu·discuss
I suffer it and that’s why I’m building https://githero.app

Btw, I worked at GitHub for 3 years and they are very aware that slowness is a big issue throughout the whole product. There was a year long cross team effort to improve things but the main goals were not achieved IMO and it shows.
gimenete
·11 bulan yang lalu·discuss
I worked there for 3 years and yes GitHub development happens on github.com. Of course there’s ways to deploy and rollback changes while the site is down but that’s very unusual. The typical flow happens in github.com and uses the regular primitives everybody uses: prs, ci checks, etc.

The pipeline for deploying the monolith doesn’t happen in GitHub Actions though but in a service based in jenkins.

Fun fact: playbooks for incidents used to be hosted in GitHub too but we moved them after an incident that made impossible to access them while it lasted.