Is GitHub down?

bad idea: "hypercarrd", a single-page website generator which ingests markdown and produces a bootable Macintosh floppy image with a stripped down System 7 and HyperCard, and packaging it with a web-based emulator to load from Github Pages

@CubeApril @hvnlyevan @LewdApril Heads up that your Twitter link on GitHub is now broken

@ramalhoorg Yeah.. I’ve been on the “*** hate train” for 10 years now, but Github made everyone forget just how terrible of a tool *** actually is. The only thing worse than *** is its man pages. VCS really doesn’t have to be this hard or error prone.

@danwalkeriv @emilyxxie @TensorFlow Make an issue on her github account.

Is Github down again?

maybe if you find an error with an addon it's not necessary to report it as a bug on curseforge and github and 3 separate channels on discord. like maybe doing one of those things would suffice. maybe

@goelajit @JoeEmison @dabit3 Sorry the suggestions in the GitHub issue didn't help and things didn't work out for you. Hope you're able you get things going in the future if you ever decide to take a look again.

@vicariousdrama Send email to support, my experience so far is mostly clutter when public issues are open. Unfortunately GitHub doesn’t have a good middle ground or moderation tools for issues.

(in case you wondered what my github issue list looks like, <3 @octoboxio)

ok @nvk, in this episode, around 1:32 the topic of checking the source to cc firmware comes up. I was having a conversation about this yesterday where your repo on github doesnt allow users to create issues. Why is that, and whats the prefferred channel to do so?

And I'm not working for my own advantage you have my GitHub.

@Niall_Boylan It should have been put up on github. Open source it and let everyone see the code. The nerds would have debated all these issues as the app was built.

@fivefilters Yeah I sussed this out on closer inspection of CSS — it comes under ".sp-message-open", as you say likely a ‘subscribe’ overlay, which on Archive appears as a white block for me. I managed to fix it within my own desktop setup — works nicely, will try put it on GitHub soonish.

"*** error: failed to push some refs to remote" wt.. *** commit --no-verify; *** push --no-verify --force " nothing to commit, working tree clean " #github

Ive been tryna figure out how to merge some features from a github project into mine. After much headache, I finally decided to just start typing, fixing blockers serially👍. So much more effective to solve problems in little bits than face the whole deal at once #100DaysOfGADS

Added docker hub publishing to my CI/CD server repo. Now publishes to npm & docker hub automatically whenever I create a GitHub release.

Announcement: Just made my first ever github pull request to a #FOSS project, that I did not start, to fix a minor bug in @qiskit ! Okay, back to the ground state.

@swyx These are literally all problems with GitHub, not monorepos.

@chrismiliki If you run `cd ~/Desktop/you2ub-jobs/react-jobs/github-jobs` (note the capital D) and restart the server from there, maybe that'll help.

So cool, a couple of hours of work and without using any server a scheduled GitHub workflow triggers a Netlify function which pulls data from a stock API and sends me an email using Mailgun. Now I need to configure it to send me weekly emails on a couple of stocks...

So cool, a couple of hours of work and without using any server a scheduled GitHub workflow triggers a Netlify which pulls data from a stock API and sends me an email using Mailgun. Now I need to configure it to send me weekly emails on a couple of stocks...

@KimStacks That's odd. Header issues? I use CloudFlare for SSL on GitHub Pages and just as a proxy/CDN for other websites.

@Uniswapgems Site is full of typos and broken English, GitHub is also scarce. Just a warning!

@dan_abramov @swyx GitHub’s “Transfer issue” is extremely helpful for this when using seperate repos. We and our users no longer stress so much about which repo an issue is *initially* raised to

@20hz20khz @100xFlutter @heroku Hey, yes I figured it out, mine was working on worker dyno. My GitHub student pack was not working at that moment but it worked later and got the free hobby dyno.

did @github just publish threads in their issues or is an A/B test ?

The year is 2020, and GitHub still lacks a keyboard shortcut or button to move between issues/pull requests. This shortcoming was the initial inspiration for creating Triage Party. I had to settle for allowing one to open all issues into new tabs, due to X-Frame-Options checks.

Day 69/#100DaysOfCode going back to the code and found all the feature that I planning to to give was almost redundant. Scratched my login arch, from GitHub as well. Gonna make it simple with login with google and twitter only. Phone number should be ultimate but not right now

@stolinski @swyx Maybe @github can add a feature to mitigate this issue for monorepos? My idea is: - Issue tracking by monorepo packages. - It would be like a kanban board where issues would be organized by each package. - Users would open new issues and select where this issue belongs.

@swyx It's a technically sound concept backed up by poor tooling, really. Github issues are barely good enough to track issues for one project, much less several. And let's face it, there aren't really great docs solutions for even single project repos.