GitHub Copilot is incredible, and if you check what’s happening in the preview released as the Copilot Labs extension it will only get more amazing.

At the end of the day, Copilot is supposed to be a tool to help developers write code faster, while ChatGPT is a general purpose chatbot, yet it still can streamline the development process, but GitHub Copilot wins hands down when the task is coding focused!

Web Monetization

Donations

This github "community of people" is apparently more interested in pontificating about pointless differences in tools and wanking off to tool complexity than they are in actually getting shit done.

[Solved] Git: LF will be replaced by CRLF the next time Git touches it’ problem solving and thinking

You can then edit files in that repository and commit and push them like this: cd 0a30d52feeb3ff60f7d8636b0bde296b # Edit files here git commit -m "Edited some files" -a git push

But if you want to be able to make local edits and then push them back, you need to use this recipe instead: git clone git@gist.github.com:0a30d52feeb3ff60f7d8636b0bde296b.git You can find this in the "Embed" menu, as the "Clone via SSH" option.

You can clone them anonymously (read-only) just using their URL: git clone https://gist.github.com/simonw/0a30d52feeb3ff60f7d8636b0bde296b

设定自定义域名：https://cdn.jsdelivr.net/gh/[github用户名]/[仓库名]@main，注意，此处的分支一定要填写@main，否则默认使用master分支。而现在github创建的默认分支名为main，如果不指定，则会出现图片不能上传的情况。【踩坑两小时】

A "pull request" is you requesting the target repository to please grab your changes. A "push request" would be the target repository requesting you to push your changes.

git commit --amend --no-edit amends a commit without changing its commit message.

Detaching HEAD just means attaching it to a commit instead of a branch

That way it would look like these two features were developed sequentially, when in reality they were developed in parallel.

git checkout da9cc5f -- README.md

Reverting The Working Copy to an Older Commit

But for all of its features, GitHub implements only a subset of git. For instance, GitHub lacks the default merge strategy of git—the fast-forward merge.

The most dangerous form of procrastination is unacknowledged type-B procrastination, because it doesn't feel like procrastination. You're "getting things done." Just the wrong things.

No to new features. No to breaking changes. No to working on holiday. No to fixing issues or merging pull requests from people who are being unpleasant. No to demands that something has to be fixed right now.

The general state of the open source ecosystem is that most maintainers are building software they want other people to use and find useful.

You can link to a particular row by clicking the row number, or select multiple rows by holding down the shift key. Just copy the URL and send it to a friend.

This is a living document. Ideas or feedback can be contributed through commenting directly using Hypothes.is which will create issues in the Github repo or you can directly create an issue: https://github.com/FAIRIslandProject/Generic-Place-based-Data-Policy/issues

The creator of CodeTriage, Richard Schneeman, was surprised to learn one day that the Ruby on Rails core team (of about 7 or so people) were responsible for handling ALL the issues opened on the Rails GitHub repo. At the time, there were about 700 or so issues. These maintainers are hugely valuable to the project due to their depth of knowledge, however keeping up with issues was taking a huge amount of time. Would you rather these highly specialized maintainers spend their time developing new features and actually fix bugs, or would you want them to spend their days responding to hundreds of issues? Asking for simple questions like "what version of Rails are you using?", and "can you provide an example app?", and "is this fixed on master?”. While asking these questions might only take 5 or 10 minutes of time, the sheer volume of issues per maintainer was unreasonable. This was highlighted by the herculean efforts of another developer Steve Klabnik, who went through every single issue and responded to all of them in a marathon session spanning multiple days. The effort got him accolades and commit access to the Rails repo. While he deserves the praise, the efforts were ultimately unsustainable.

getting set up requires a github account and “pushing” commits every time I write a post

Why Microsoft Is Willing to Pay So Much for GitHub by Paul V. Weinstein

Jun 6, 2018 — Microsoft's $7.5 billion acquisition of GitHub is a perfect illustration of how value is ascribed differently in Silicon Valley than in the ...github microsoft acquisitionwhy did microsoft buy githubwhy did microsoft buy github redditmicrosoft github strategygithub revenuewho owned github before microsoftPeople also search for

Microsoft to acquire GitHub for $7.5 billion

Microsoft acquires GitHub

Microsoft acquired GitHub, a popular code-repository service used by many developers and large companies, for $7.5 billion in stock.

it's very easy to measure how many github back and forths people have

Free public projects private projects starting at $9/month per project

Overall, if speed is your primary concern and you’re on a budget, then Circle CI is the clear choice. If you’re not looking to run a ton of builds each month and your code is already in Github, then Github Actions can offer similar performance with the added convenience of having everything under one service. Even though we liked Travis better, our main criteria was value, and since you can’t use Travis for free after the first month, GitLab was able to grab the third slot, despite it being weaker in almost every other category.

We overload the meaning of "GFM" to mean "GitLab Flavored Markdown", which is a superset of GitHub's version. However it can cause confusion as they are not the same thing.

That people show off these illegible globs in public only makes sense from a signaling perspective: They are saying, “look at how many nodes I have in my brain, amazing nodes

Markdown's supported, as long as you have a blank line between the </summary> tag and the following content.

a way for us to compare, restore, and merge changes to our stuff.

I can enjoy my hobby in open-source without Github issues becoming a shouting match that spans 200 comments from people who aren't even invested in the codebase

Except it sucks for everybody who's left out.

While it's true that GitHub has become more accessible to non-programmers than it once was, these folks won't be comfortable making pull requests anytime soon.

Gist.io isWriting for HackersThere’s a scale of permanence to writing on the web. On one end, we have the tweet: brief and ephemeral. On the other end of the scale, we have longform blog writing: unlimited in length and hopefully impervious to the passage of time.Sometimes, we want to share a bit of writing that is neither. Maybe we want to write for a specific audience, but don’t want to address the people who usually read our blogs. Maybe it’s just something that doesn’t fit into 140 characters.Gist.io is a solution for that, inspired by Mike Bostock’s delightful bl.ocks.org

On the Web, the file extension doesn’t really matter

Massive Wiki is a movement to create a wiki ecosystem (rather than just one engine) that provides classic wiki utility, with a plurality of tools and processes that enable decentralization and federation of the pages.

And back in the day, everything was GitHub issues. The company internal blog was an issue-only repository. Blog posts were issues, you’d comment on them with comments on issues. Sales deals were tracked with issue threads. Recruiting was in issues - an issue per candidate. All internal project planning was tracked in issues.

I mean, over 40M devs from over 41 countries on GitHub? Pretty amazing.

linking from preprints to their journal version 

https://github.com/propublica/compas-analysis/blob/master/Compas%20Analysis.ipynb

GitHub Actions is GitHub’s platform for automation workflows. A workflow is a sequence of jobs that can run either in series or in parallel. A job usually contains more than one step, where each step is a self-contained function. To learn more about GitHub Actions, go through the tutorial on Continuous Integration for Android.

My favorite part of this entire plan has to be the part where I use Github Issues as a blog. Kind of. For every new feature (or set of features) I want to add to the site—no matter how small, like adding a Favicon, for example—I will open a new issue and create a corresponding branch where the work on that feature will happen. I will basically produce a(n) infrequent stream of short “blog posts” in the form of Github issues. The live code for each issue/feature will live in the issue’s corresponding branch. As someone who tends to do multiple things at once, this will take a lot of organization and discipline, and that’s the challenging part for me.

Dev Environments Built for the Cloud.

A cheatsheet on the usage of git flow, visit http://danielkummer.github.com/git-flow-cheatsheet/

TL;DR for developer documentation - a ridiculous collection of cheatsheets

The model is trained on 147M multi-turn dialogue from Reddit discussion thread. The largest model can be trained in several hours on a 8 V100 machines (however this is not required), with distributed training and FP16 option.

Types of GitHub Pages sites

Host on GitHub

Deployment of Project Pages from /docs folder on main branch

OpenApiValidators

I feel that with all that power that it’s gaining, instead of being a more approachable tool, that it’s actually being a tool that is continuously making people feel frustrated, to the point where I feel that whatever the next version control system is… (And it does not have to be something separate than Git. It should maybe be just a really powerful abstraction built on top of Git.) But I think whatever the next iteration of the people’s version control is… it should be something that is more reflective of how we think about what version control is for us.

GitHub App

Your weekly reminder that1. You should not have your development process on a centralized platform, at least not if you're doing anything that smells of copyright issues2. If you do host on a centralized platform, have regular, decentralized backups of code and issue tracking.3. Also, avoid US-centric hosting for this kind of thing. But really, refer to 1.

You can invite users to become collaborators to your personal repository.

Lastly, I walked through Github Pages, and how using a separate branch, you can publish HTML, CSS, JavaScript and JSON for projects, turning Github into not just a code and content management platform, but also a publishing endpoint.