Is Changelog CI a new service offering from your favorite news feed providers?! Nope!
Is Changelog CI a way to generate a changelog via carefully crafted PR titles? Yep!
Is auto-generating your project’s changelog a good idea? Maybe…
Is Changelog CI a new service offering from your favorite news feed providers?! Nope!
Earlier this year on February 2nd, 2020 Jon Evans and his team of archivists took a snapshot of all active public repositories on GitHub and sent it to a decommissioned coal mine in the Svalbard archipelago where it will be stored for the next 1,000 years.
On this episode, Jon chats with Jerod all about the GitHub Archive Program and how they’re preserving open source software for future generations.
Following Git 2.28’s highly sought after ability to configure
init.defaultBranch comes GitHub’s support at the platform level.
You can now set the default branch name for newly-created repositories under your username. This setting does not impact any of your existing repositories. Existing repositories will continue to have the same default branch they have now.
But even if you do nothing…
On October 1, 2020, if you haven’t changed the default branch for new repositories for your user, organization, or enterprise, it will automatically change from
Two days ago on this repo appeared on the top starred repositories first timers list on Changelog Nightly…
In this repository, you can find the official GitHub public product roadmap. Our product roadmap is where you can learn about what features we’re working on, what stage they’re in, and when we expect to bring them to you.
The roadmap repository is for communicating GitHub’s roadmap. Existing issues are currently read-only, and we are locking conversations, as we get started. Interaction limits are also in place to ensure issues originate from GitHub. We’re planning to iterate on the format of the roadmap itself, and we see potential to engage more in discussions about the future of GitHub products and features.
Leading off the updates for Git 2.28 is the highly sought after ability to configure
init.defaultBranch so folks can move from
main as their default branch name.
From Taylor Blau on the GitHub blog:
When you initialize a new Git repository from scratch with
git init, Git has always created an initial first branch with the name
master. In Git 2.28, a new configuration option,
init.defaultBranchis being introduced to replace the hard-coded term. (For more background on this change, this statement from the Software Freedom Conservancy is an excellent place to look).
Starting in Git 2.28,
git initwill instead look to the value of
init.defaultBranchwhen creating the first branch in a new repository. If that value is unset,
GitHub Sponsors is a step forward, but is far from a panacea. I propose “sponsorship pools”, an alternative approach to OSS sustainability.
I thought it’d be cool to get
mix test and
mix format running on pushes to the changelog.com repo, so I gave GitHub Actions the old college try. After (not too much) futzing around on my own, I figured I’d have more success by getting an expert to help out. Good call be me! 😆
Copy and paste this Markdown into your readme, swap the
username, and you’re up and running:
[![Anurag's github stats](https://github-readme-stats.vercel.app/api?username=anuraghazra)](https://github.com/anuraghazra/github-readme-stats)
I think we’ll be seeing many more
Dynamically generated $X for your GitHub readme repos pop up over the coming weeks.
Monical Powell has a great rundown of GitHub’s new profile readme feature. She lays out how to set up yours and then lists a bunch of creative ways our fellow devs are using theirs. Video games, GitHub Actions, and Spotify playlists abound.
This insight by Aaron Schlesinger on the latest Go Time is on point (IMHO), and realizing this relationship between the two social networks might change the way you think about code on GitHub…
I am now making more money than I’ve ever made while developing open-source software for a community that I adore. Pinch me, I’m dreaming.
Was it luck? there’s certainly been a lot of that.
Was it fate? Let’s leave religion out of this mmkay?…
Was it that the software I built was so incredibly compelling that it forced 535 people to give me at least $14/mo. to keep working on it? …I wish.
It’s more than that though. There were some key things I did along the way to get here. Let me tell you all about them.
Use this GitHub Action to select a combination of linters you want to run on your code base automatically. It currently supports 15 linters and there are a bunch more in the request queue.
At first I thought it was just me getting older and more experienced. But after several conversations about it with colleagues and other open source maintainers, I’m not the only one who feels this way.
After a lot of reflection, I believe the turning point was when they changed how the ranking system on the Trending page worked.
I don’t know if I ever considered GitHub fun, but I agree the trending section has lost value over the years. You know what is fun, though? Getting the day’s hottest new & trending repos delivered directly to your inbox. That’s what. 😉
Sid Sijbrandij is the Co-founder and CEO of GitLab — an all-remote company and complete DevOps platform. As a company, they have their eyes set on taking the company public to IPO and they’re very outspoken about their culture, open handbook, and how they work as an all-remote company. We talk through where Sid came from, the early days of GitLab, why IPO vs a private sale (like GitHub), what it means to put “family and friends first, work second,” how we should view work, and his biggest fear — the company failing.
Johnny and Jon are joined by Denise to talk about her role at GitHub and what the community and safety team does to help open source project creators and contributors, GoCon Canada and the role of organizing a conference, and more.
Jason Warner (CTO at GitHub) joined the show to talk with us about the backstory of how he helped to lead GitHub to a $7.5 billion acquisition by Microsoft. Specifically how they trusted their gut not just the data, and how they understood the value they were bringing to market. We also talk about Jason’s focus on “horizon 3” for GitHub, and his thoughts on remote work and how they’re leading GitHub engineering today.
May 7th, 2020: A discussion appears on Atom’s forum…
I use Atom for a few years now and was worried back then about the acquisition of Github from Microsoft. And now I read about Github Codespaces, which is powered by Visual Studio Code.
I’m a little concerned about this. Do you still support Atom? And do you support Atom in the future? If there are other opportunities of embedding a Editor or innovating would you also choose VS Code over Atom?
What is the future of Atom? Will you slowly move to VS Code and Atom will be on the support line?
All good questions. There’s been no official (or unofficial, that I’ve seen) response from GitHub just yet.
We’ve been following Atom for years now. Many great developers have put their efforts into the editor. But it’s hard to withstand the gravitational pull of VS Code. Even more so now that Microsoft owns GitHub? 🤔
InfoQ has a nice rundown of all that GitHub announced at Satellite this week. On Codespaces:
Codespaces gives you a fully-featured, cloud-hosted dev environment that spins up in seconds, directly within GitHub, so you can start contributing to a project right away.
At the heart of Codespaces lies Visual Studio Code running in your browser, so you get code completion, extensions, code navigation, and the rest of Visual Studio Code features you are used to.
GitHub Discussions appear very similar to Issues and Pull Requests on the outside, but they aim to go beyond the linear structure of the latter by supporting a threaded questions and answers format. According to GitHub, this should make it easier to organize an otherwise unstructured conversation and build a persistent knowledge base.
I’m personally not too excited about either of these features. I think Codespaces could be a big deal for casual contributions, but those are the lowest form of contribution. Discussions seems like a direct shot at StackOverflow, which makes good business sense, but I wonder if it will get mired in the Issues/Pull Requests/Wikis mucky muck.
In this post Arthur covers the core concepts, the question “Should you use GitHub Actions?”, and a step-by-step tutorial to build a functional CI/CD pipeline using GitHub Actions.
If you are already using GitHub to host your project’s source code, getting started with GitHub Actions is effortless. The fact that it integrates fully with the entire GitHub ecosystem means your team can double down on using the platform as a significant part of your software development process.
Overall, my opinion is that GitHub Actions is worth a try. Whether this is the automation system best suited for your team depends on your specific needs.
This.. is a bit of a bombshell:
Software is eating the world. Meanwhile, Microsoft is eating the software world… one acquisition at a time.
To answer the question in the headline:
- I find the GitLab UI to be cleaner in general and easier to find my way around. However, this is purely a matter of taste and probably not a strong reason to move.
- I also like how GitLab is open source. I am far from an open source zealot, but I do prefer to write and use open source software. While Github is full of Open Source projects, Github itself is proprietary. In contrast, Gitlab has a well-supported open source version.
- The project import feature worked very well, so it was trivially easy to move the code, branches and issues over.
The author goes on to describe why GitLab’s project management workflow works well for him.
A handy little web app for quickly finding the
droids code you’re looking for.
grep.app searches code from over a half million public repositories on GitHub. We’re hoping to add more soon…
It searches for the exact string you enter, including any punctuation or other characters. You can also search by regular expression, using the RE2 syntax.
GistPad is a Visual Studio Code extension that allows you to manage GitHub Gists entirely within the editor. You can open, create, delete, fork, star and clone gists, and then seamlessly begin editing files as if they were local.
The big idea here is to use gists to seamlessly create your “very own developer library”. The interactive playgrounds is pretty cool, too.
gh brings many of GitHub’s concepts to the terminal. You know, things like pull requests and issues. The tool is still under heavy development and they’re looking for feedback. If you’re an early adopter, this is the perfect time to get involved and let your voice be heard. Oh, and if you’ve been using hub for years already, here’s how the new shiny compares:
ghis a new project for us to explore what an official GitHub CLI tool can look like with a fundamentally different design. While both tools bring GitHub to the terminal,
hubbehaves as a proxy to
ghis a standalone tool.